Difference between revisions of "StarlingX/Packet SIG"
Greg-waines (talk | contribs) (→Packet SIG) |
Greg-waines (talk | contribs) m (→Packet SIG) |
||
Line 18: | Line 18: | ||
** Results in StartingX Maintenance reporting a false alarm that it has lost connectivity with other nodes in the StarlingX Cloud. E.g. In Central Cloud, cc-controller-0 claims that it has a heartbeat audit failure with cc-controller-1. | ** Results in StartingX Maintenance reporting a false alarm that it has lost connectivity with other nodes in the StarlingX Cloud. E.g. In Central Cloud, cc-controller-0 claims that it has a heartbeat audit failure with cc-controller-1. | ||
** WORKAROUND: Change maintenance's heartbeat failure behaviour to simply raise an alarm ... rather than declare the node as failed and try to reset. | ** WORKAROUND: Change maintenance's heartbeat failure behaviour to simply raise an alarm ... rather than declare the node as failed and try to reset. | ||
+ | <pre> | ||
system service-parameter-list | system service-parameter-list | ||
system service-parameter-modify platform maintenance heartbeat_failure_action=alarm | system service-parameter-modify platform maintenance heartbeat_failure_action=alarm | ||
system service-parameter-apply platform | system service-parameter-apply platform | ||
+ | </pre> | ||
<br /> | <br /> | ||
Problems Found with StarlingX R1.0:<br /> | Problems Found with StarlingX R1.0:<br /> |
Revision as of 16:36, 5 July 2019
Contents
Packet SIG
Packet.com is a baremetal public cloud, and they have donated some resources to the StarlingX project. The resources are available under the STX-PROJECT-01 project on Packet.com.
StarlingX Distributed Cloud on Packet.Com
As a demonstration of the OpenStack Edge Computing Group's Distributed Control Plane MVP Architecture, StarlingX Distributed Cloud has been deployed on Packet.com.
STX R1
Horizon for Central Cloud: http://147.75.105.202
SSH to Central Cloud: ssh wrsroot@147.75.105.202
Problems Found with Packet.com:
- Multi-cast Packets appear to be dropped by Packet.com switches
- Results in StartingX Maintenance reporting a false alarm that it has lost connectivity with other nodes in the StarlingX Cloud. E.g. In Central Cloud, cc-controller-0 claims that it has a heartbeat audit failure with cc-controller-1.
- WORKAROUND: Change maintenance's heartbeat failure behaviour to simply raise an alarm ... rather than declare the node as failed and try to reset.
system service-parameter-list system service-parameter-modify platform maintenance heartbeat_failure_action=alarm system service-parameter-apply platform
Problems Found with StarlingX R1.0:
Packet.com Servers deployed
Networking
Installing the Central Cloud
Blah, blah, blah.