Closed asimkhawaja closed 8 years ago
Hi @asimkhawaja it's hard to read the logs. Can you edit the message to use the pre-formatted syntax in Markdown please? https://help.github.com/articles/working-with-advanced-formatting/
No worries. Is that better?
I think what the issue may be. I am running plumbery from my local machine agasint CaaS. I need to perhaps run it directly on the CaaS as per this comment in the polisher file:
In the real life when you have to prepare any appliance, you need to be close
to the stuff and to touch it. This is the same for virtual fittings.
This polisher has the need to communicate directly with target
nodes over the network.
This connectivity can become quite complicated because of the potential mix
of private and public networks, firewalls, etc. To stay safe plumbery
enforces a simple beachheading model, where network connectivity with end
nodes is a no brainer.
This model is based on predefined network addresses for plumbery itself,
as in the snippet below::
---
# Frankfurt in Europe
locationId: EU6
regionId: dd-eu
# network subnets are 10.1.x.y
prepare:
- beachhead: 10.1.3.4
Here nodes at EU6 will be prepared only if the machine that is
executing plumbery has the adress 10.1.3.4. In other cases, plumbery will
state that the location is out of reach.
You can run the docker container in CaaS or connect to the VPN
Sent from Outlook Mobile
On Mon, May 2, 2016 at 6:44 PM -0700, "asimkhawaja" notifications@github.com wrote:
I think what the issue may be. I am running plumbery from my local machine agasint CaaS. I need to perhaps run it directly on the CaaS as per this comment in the polisher file:
In the real life when you have to prepare any appliance, you need to be close
to the stuff and to touch it. This is the same for virtual fittings.
This polisher has the need to communicate directly with target
nodes over the network.
This connectivity can become quite complicated because of the potential mix
of private and public networks, firewalls, etc. To stay safe plumbery
enforces a simple beachheading model, where network connectivity with end
nodes is a no brainer.
This model is based on predefined network addresses for plumbery itself,
as in the snippet below::
---
# Frankfurt in Europe
locationId: EU6
regionId: dd-eu
# network subnets are 10.1.x.y
prepare:
- beachhead: 10.1.3.4
Here nodes at EU6 will be prepared only if the machine that is
executing plumbery has the adress 10.1.3.4. In other cases, plumbery will
state that the location is out of reach.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub
I am now able to get to a stage where the beachead network is working when i run it from a VM in CaaS. But now it seems like cloud-init is just not executing the instructions on the machine. Will close and make a new ticket for this next problem
@asimkhawaja , some clarification coming lately. Cloud-config requires SSH connectivity between the node that is running plumbery and the target node. There are at least too common ways to ensure this:
This would deserve more comprehensive explanations in the on-line documentation, of course. Many thanks for your efforts on plumbery :-)
Hey Folks, I am unable to use cloud-config in my fittings file. Running with the -d setting shows that when plumbery tries to use cloud-config it get a node unreachable. I have based my simplified fittings file based on the more complex files in the samples project, so I might be missing something.
Your guidance would be most appreciated.
Fittings file used:
plumbery output: