Comments (1)
The VSM IP needs to remain static (sticky) today, because the client that is connected to VSM IP may not know that IP address has changed due to HA or Migration.
The workflow is as follows:
(1) When VSM is created, an IP is allocated on the required network segment ( subnet/vlan)
(2) This allocated IP needs to be persisted ( in nameserver for service discovery) and accessible via the API / command response to pass on to the client.
(3) The client connects using the IP
(4) HA/Migration causes the VSM to be moved to another node
(5) The IP on the old node needs to be cleared ( if node is still online)
(6) The IP needs to be created on the new node, before the VSM is started
To support this use case in the current scheme of things, where we don't have post/pre hooks for nomad docker containers, i will be using a wrapper approach that will do the (2),(5),(6).
hashicorp/nomad#1061
https://gist.github.com/ketzacoatl/3ccf5bb822df51aed2b896641e931c8a
https://github.com/FRosner/nomad-docker-wrapper
http://stackoverflow.com/questions/34688906/how-to-assign-static-public-ip-to-docker-container
(Also when we get the flannel or any other networking plugin working, we will need to modify it to allow for sticky IPs. This is currently not on the road-maps for containers-network-plugins. )
In the future, we may be eliminate this Sticky IP Requirement for VSMs, if the client can use the "service discovery" of the container world or "iSNS" to know of the VSM IP
(a) When VSM is created, an IP is allocated on the required network segment ( subnet/vlan)
(b) This allocated IP needs to be persisted ( for service discovery)
(c) The client is passed an domain name (key) for the volume and it uses the iSNS or Service discovery to know the IP address to connect to.
(d) On HA/Migration the VSM can come up on new up and it will update - name server/iSNS. Client will reconnect with the updated IP address.
For the containers use-case, the above can be implemented because maya-driver can query for the VSM IP address and reconnect.
For non-container cases, where client side driver is not available - we can use the iSCSI - iSNS functionality (This is what I think solidfire uses).
For use cases, where VSM can move across environments like hybrid-cloud, the domain name based option may become mandatory.
Is there any case where this changed implementation can become a bottleneck?
Is there any better way to eliminate this sticky IP requirement? ( using a client side load-balancer .. but requires that the VSM comes up from a pool of IPs allocated during creation )
from maya.
Related Issues (20)
- Insecure default permissions in /var/openebs HOT 2
- Local PV support for ReadWriteMany HOT 8
- The arm arch cannot use the ScrubImage to clean up pvc volume. HOT 4
- build cstor for armοΌ cannot create cstor pool
- CONTRIBUTING.md: Fix `faimilar` typo
- Can we move this code to different file.. like `cstor_debug.go`? It will be good to have structured code..
- CGO_ENABLED=1 makes cspc-operator can't run in alpine HOT 5
- Set tolerations for Jiva Scrubimage job's pod HOT 1
- refactor cstorcompletedbackup and cstorbackup spec HOT 2
- BDD for Local PV Block device with tag.
- BDD: Local PV hostpath for hostname label change.
- restore completed successfully but one of the replica was not having the snapshot restored
- restic restore failed for cstor volume HOT 3
- refactoring needed to add support for go modules.
- bug unable to find BD: for BDC HOT 2
- zpool and zfs command execution using CSP HOT 2
- "admission-webhook.openebs.io" does not support dry run HOT 5
- cStor (non-CSI): GitHub Updates
- Jiva (non CSI): GitHub updates
- no node was specified
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from maya.