On 2017-04-03 19:32:42 +0200 (+0200), Alex Burmashev wrote:
[...]
> Now i have to figure out why private IP is considered as public...
[...]
There are a number of potential reasons, and the logic behind that
decision is encapsulated in the shade.meta.get_server_external_v4()
function:
http://git.
Follow up:
i have added some crude debug to
/usr/local/lib/python2.7/dist-packages/shade/openstackcloud.py and seems
that private ip is really treated as public, this condition is triggered:
if server['public_v4']:
return False
so basically shade figures out that started
On 2017-04-03 17:21:24 +0200 (+0200), Alex Burmashev wrote:
> Yeah, i thought about it, but i think automatic IP assigning is only
> supported with nova-network, and i use neutron.
>
> Moreover at least for some time nodepool definitely was assigning IPs to the
> VMs, it is starting, it is mention
Yeah, i thought about it, but i think automatic IP assigning is only
supported with nova-network, and i use neutron.
Moreover at least for some time nodepool definitely was assigning IPs to
the VMs, it is starting, it is mentioned in docs, maillists and irc
discussions. Maybe at some moment a
If I am not mistaken,
You can configure your cloud/network to assign automatically floating IP to the
VM.
This is related to the cloud and not to the nodepool
-Original Message-
From: Alex Burmashev [mailto:alexander.burmas...@oracle.com]
Sent: Monday, April 3, 2017 6:03 PM
To: Lenny Ve
Hi!
* private ip is assigned without a problem automatically.
* VM is inaccessible from the external network using private IP,
available from inside the private network. Which is normal, i think.
When i manually assign public IP, machine is accessible via that public
IP from elsewhere.
* T
On 2017-04-03 16:35:58 +0900 (+0900), Masahito MUROI wrote:
> I've pushed the change[1] to project-config repo and it's already been
> merged. However, the change fails to be applied to gerrit board. I heard the
> reason of the failure is some bugs happend in infra.
It looks applied to me at this
Hi Alex,
Please set DEBUG level in nodepool to see more info
Few questions:
Do you get private ip?
Can you ping the vm?
What is the failure?
-Original Message-
From: Alex Burmashev [mailto:alexander.burmas...@oracle.com]
Sent: Monday, April 3, 2017 4:03 P
Hello!
I am setting up a CI instance and currently face a problem with
auto-assigning floating IPs.
Instances are started, no error in /var/log/nodepool/debug.log, but
floating ip is not assigned and nodepool tries to access instance via
private ip, and it fails obviously.
Manual IP assign
Hello infra team,
I've pushed the change[1] to project-config repo and it's already been
merged. However, the change fails to be applied to gerrit board. I heard
the reason of the failure is some bugs happend in infra.
Where should I track or report the failure? I couldn't fine the launchpa
10 matches
Mail list logo
