WO2019220173A1 - Distributed snapshot of rack - Google Patents
Distributed snapshot of rack Download PDFInfo
- Publication number
- WO2019220173A1 WO2019220173A1 PCT/IB2018/053401 IB2018053401W WO2019220173A1 WO 2019220173 A1 WO2019220173 A1 WO 2019220173A1 IB 2018053401 W IB2018053401 W IB 2018053401W WO 2019220173 A1 WO2019220173 A1 WO 2019220173A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- snapshot
- rack
- token
- distributed
- spine switch
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
Definitions
- the Distributed Snapshot Service will generate a snapshot token consisting of the rack identifier and timestamp of the system where the Distributed
- Snapshot Service is running.
- the generated snapshot token will be forwarded to the cloud component consisting of the entry point for the packets of the rack or the spine switch of the rack connecting all the different cloud components of the rack like virtual switching nodes, virtual compute nodes, virtual storage nodes, etc.
- the spine switch of the rack will forward the snapshot token to all different cloud components of the rack and the messages or events that have to be considered for the distributed snapshot will be tagged with the snapshot token by the spine switch and subsequently other components in the rack will tag the snapshot token as well for events or messages generated due to the above spine switch snapshot token tagged event or message.
- the cloud components of the rack will independently take their snapshots and tag it with the snapshot token and component identifier, and send it to the remote Distributed Snapshot Service.
Abstract
Here when we are required to take distributed snapshot of a rack, the Distributed Snapshot Service will generate a snapshot token consisting of the rack identifier and a local timestamp. The generated snapshot token will be forwarded to the spine switch connecting all the different cloud components of the rack. The spine switch of the rack will forward the snapshot token to all different cloud components of the rack and the messages or events that have to be considered for the distributed snapshot will be tagged with the snapshot token by the spine switch. The cloud components of the rack will independently take their snapshots and tag it with the snapshot token and component identifier, and send it to the remote Distributed Snapshot Service.
Description
Distributed Snapshot of Rack
In this invention we provide distributed snapshot of different subsystems of the cloud like virtual switching nodes, virtual compute nodes and virtual storage nodes held by the rack. When we are required to take distributed snapshot of a rack, the Distributed Snapshot Service will generate a snapshot token consisting of the rack identifier and timestamp of the system where the Distributed
Snapshot Service is running. The generated snapshot token will be forwarded to the cloud component consisting of the entry point for the packets of the rack or the spine switch of the rack connecting all the different cloud components of the rack like virtual switching nodes, virtual compute nodes, virtual storage nodes, etc. The spine switch of the rack will forward the snapshot token to all different cloud components of the rack and the messages or events that have to be considered for the distributed snapshot will be tagged with the snapshot token by the spine switch and subsequently other components in the rack will tag the snapshot token as well for events or messages generated due to the above spine switch snapshot token tagged event or message. The cloud components of the rack will independently take their snapshots and tag it with the snapshot token and component identifier, and send it to the remote Distributed Snapshot Service.
Claims
1. In this invention we provide distributed snapshot of different subsystems of the cloud like virtual switching nodes, virtual compute nodes and virtual storage nodes held by the rack. When we are required to take distributed snapshot of a rack, the Distributed Snapshot Service will generate a snapshot token consisting of the rack identifier and timestamp of the system where the Distributed Snapshot Service is running. The generated snapshot token will be forwarded to the cloud component consisting of the entry point for the packets of the rack or the spine switch of the rack connecting all the different cloud components of the rack like virtual switching nodes, virtual compute nodes, virtual storage nodes, etc. The spine switch of the rack will forward the snapshot token to all different cloud components of the rack and the messages or events that have to be considered for the distributed snapshot will be tagged with the snapshot token by the spine switch and subsequently other components in the rack will tag the snapshot token as well for events or messages generated due to the above spine switch snapshot token tagged event or message. The cloud components of the rack will independently take their snapshots and tag it with the snapshot token and component identifier, and send it to the remote Distributed Snapshot Service. The above novel technique of taking Distributed Snapshot of the rack holding different cloud components is the claim for this invention.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2018/053401 WO2019220173A1 (en) | 2018-05-16 | 2018-05-16 | Distributed snapshot of rack |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB2018/053401 WO2019220173A1 (en) | 2018-05-16 | 2018-05-16 | Distributed snapshot of rack |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019220173A1 true WO2019220173A1 (en) | 2019-11-21 |
Family
ID=68539619
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2018/053401 WO2019220173A1 (en) | 2018-05-16 | 2018-05-16 | Distributed snapshot of rack |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2019220173A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113242158A (en) * | 2021-05-10 | 2021-08-10 | 上海华讯网络系统有限公司 | Real-time monitoring method and system based on switch hardware timestamp |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110258461A1 (en) * | 2010-04-16 | 2011-10-20 | Twinstrata, Inc | System and method for resource sharing across multi-cloud arrays |
US8489831B2 (en) * | 2008-10-01 | 2013-07-16 | Hewlett-Packard Development Company, L.P. | Systems and methods for data snapshot replication using a token in a replication link |
-
2018
- 2018-05-16 WO PCT/IB2018/053401 patent/WO2019220173A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8489831B2 (en) * | 2008-10-01 | 2013-07-16 | Hewlett-Packard Development Company, L.P. | Systems and methods for data snapshot replication using a token in a replication link |
US20110258461A1 (en) * | 2010-04-16 | 2011-10-20 | Twinstrata, Inc | System and method for resource sharing across multi-cloud arrays |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113242158A (en) * | 2021-05-10 | 2021-08-10 | 上海华讯网络系统有限公司 | Real-time monitoring method and system based on switch hardware timestamp |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2007027679A3 (en) | Method and system for reliable message delivery | |
WO2016157134A3 (en) | Vehicle event recording system and method | |
WO2019072294A3 (en) | Achieving consensus among network nodes in a distributed system | |
WO2015119895A8 (en) | Bandwidth and latency estimation in a communication network | |
WO2019226986A8 (en) | Nested blockchain system | |
WO2012079026A3 (en) | System and method for providing improved failover performance for pseudowires | |
MX2008015150A (en) | Failover/failback trigger using sip messages in a sip survivable configuration. | |
WO2016179235A8 (en) | Systems and methods for ephemeral group chat | |
WO2006134373B1 (en) | Reception according to a data transfer protocol of data directed to any of a plurality of destination entities | |
CN105745883B (en) | Forwarding table synchronous method, the network equipment and system | |
MX2019014416A (en) | 360-degree video delivery over next generation network. | |
ATE489791T1 (en) | STATE UPDATE IN EDGE ROUTERS | |
JP2011053918A5 (en) | ||
WO2010021984A3 (en) | Method and systems for redundant server automatic failover | |
WO2008106361A3 (en) | Hierarchical temporal memory (htm) system deployed as web service | |
WO2008120267A1 (en) | Edge node redundant system | |
WO2014018556A3 (en) | Messaging between web applications | |
WO2012051366A3 (en) | Ordered processing of groups of messages | |
WO2010080533A3 (en) | Multipurpose storage system based upon a distributed hashing mechanism with transactional support and failover capability | |
JP2011166758A5 (en) | ||
WO2016148730A3 (en) | Restoring a flow path in response to a link failure in a software defined network (sdn) | |
WO2014110174A8 (en) | Systems and methods for transporting a clock signal over a network | |
WO2008108474A1 (en) | Reachability realizing server, management system, management method and realization program | |
EP2945350A3 (en) | Communication apparatus, a system for secure communication, and a method for communication | |
PH12019502713A1 (en) | Multi-connection recovery method in non-activated state and device therefor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18919338 Country of ref document: EP Kind code of ref document: A1 |