[Openstack-operators] [openstack-dev] [openstack-ansible] pip issues
Achi Hamza
h16mara at gmail.com
Thu Nov 17 15:07:22 UTC 2016
It also works on the Public IP of the repo:
root at maas:/opt/openstack-ansible/playbooks# ansible hosts -m shell -a "curl
http://*172.16.1.222*:8181/os-releases/"
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e
@/etc/openstack_deploy/user_variables.yml "
node01 | SUCCESS | rc=0 >>
<html>
<head><title>Index of /os-releases/</title></head>
<body bgcolor="white">
<h1>Index of /os-releases/</h1><hr><pre><a href="../">../</a>
<a href="14.0.1/">14.0.1/</a>
16-Nov-2016 14:47 -
</pre><hr></body>
</html> % Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent Left
Speed
100 287 0 287 0 0 381k 0 --:--:-- --:--:-- --:--:--
280k
do you have an explanation to this Jesse ?
Thank you
On 17 November 2016 at 15:53, Achi Hamza <h16mara at gmail.com> wrote:
> It also works on the internal interface of the containers, i can fetch
> from the repo container to the host on the internal IP of the container:
>
> *root at maas:/opt/openstack-ansible/playbooks# ansible hosts -m shell -a
> "curl http://10.0.3.92:8181/os-releases/
> <http://10.0.3.92:8181/os-releases/>"*
> Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e
> @/etc/openstack_deploy/user_variables.yml "
> node01 | SUCCESS | rc=0 >>
> <html>
> <head><title>Index of /os-releases/</title></head>
> <body bgcolor="white">
> <h1>Index of /os-releases/</h1><hr><pre><a href="../">../</a>
> <a href="14.0.1/">14.0.1/</a>
> 16-Nov-2016 14:47 -
> </pre><hr></body>
> </html> % Total % Received % Xferd Average Speed Time Time
> Time Current
> Dload Upload Total Spent Left
> Speed
> 100 287 0 287 0 0 405k 0 --:--:-- --:--:-- --:--:--
> 280k
>
>
> On 17 November 2016 at 15:26, Achi Hamza <h16mara at gmail.com> wrote:
>
>> It works on the repo itself:
>>
>> *root at maas:/opt/openstack-ansible/playbooks# ansible repo_all -m shell -a
>> "curl http://localhost:8181/os-releases/
>> <http://localhost:8181/os-releases/>"*
>> Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e
>> @/etc/openstack_deploy/user_variables.yml "
>> node01_repo_container-82b4e1f6 | SUCCESS | rc=0 >>
>> <html>
>> <head><title>Index of /os-releases/</title></head>
>> <body bgcolor="white">
>> <h1>Index of /os-releases/</h1><hr><pre><a href="../">../</a>
>> <a href="14.0.1/">14.0.1/</a>
>> 16-Nov-2016 14:47 -
>> </pre><hr></body>
>> </html> % Total % Received % Xferd Average Speed Time Time
>> Time Current
>> Dload Upload Total Spent Left
>> Speed
>> 100 287 0 287 0 0 59878 0 --:--:-- --:--:-- --:--:--
>> 71750
>>
>>
>> On 17 November 2016 at 15:22, Jesse Pretorius <
>> Jesse.Pretorius at rackspace.co.uk> wrote:
>>
>>>
>>>
>>>
>>>
>>> *From: *Achi Hamza <h16mara at gmail.com>
>>> *Date: *Thursday, November 17, 2016 at 1:57 PM
>>> *To: *Jesse Pretorius <Jesse.Pretorius at rackspace.co.uk>, "
>>> OpenStack-operators at lists.openstack.org" <OpenStack-operators at lists.ope
>>> nstack.org>
>>> *Subject: *Re: [Openstack-operators] [openstack-dev]
>>> [openstack-ansible] pip issues
>>>
>>>
>>>
>>> Thank you Jesse, but these iptables rules are just applied on the
>>> deployment node not the host nodes. do i have to omit these rules even on
>>> the deployment node ?
>>>
>>>
>>>
>>> Thank you
>>>
>>>
>>>
>>> Ah, then that’s a red herring. As long as your hosts can reach the
>>> internet through it, then you’re good on that front.
>>>
>>>
>>>
>>> Let’s go back to verifying access to the repo – try checking access from
>>> the repo server to itself:
>>>
>>>
>>>
>>> ansible repo_all -m uri -a "url=http://localhost:8181/os-releases/"
>>>
>>>
>>>
>>> or
>>>
>>>
>>>
>>> ansible repo_all –m shell –a "curl http://localhost:8181/os-releases/"
>>>
>>>
>>>
>>> ------------------------------
>>> Rackspace Limited is a company registered in England & Wales (company
>>> registered number 03897010) whose registered office is at 5 Millington
>>> Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy
>>> can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail
>>> message may contain confidential or privileged information intended for the
>>> recipient. Any dissemination, distribution or copying of the enclosed
>>> material is prohibited. If you receive this transmission in error, please
>>> notify us immediately by e-mail at abuse at rackspace.com and delete the
>>> original message. Your cooperation is appreciated.
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161117/f268c719/attachment.html>
More information about the OpenStack-operators
mailing list