[ansible-project] Galaxy 3.2 release scheduled for Monday, 3 June

[Chris Houseknecht]

The Galaxy team will be deploying version 3.2 this coming Monday, 3 June 
2019. The release process will begin at 4 AM Eastern on Monday and complete 
no later than 6 AM. We don't anticipate any significant downtime, but 
should problems arise, watch for updates on the Ansible mailing lists.

To see what's new, try it out live on our QA site at 
https://galaxy-qa.ansible.com, and view our changelog 
<https://github.com/ansible/galaxy/blob/devel/CHANGELOG.rst> for all the 
details.

Please feel free to share your feedback by opening an issue 
<https://github.com/ansible/galaxy/issues/new/choose> at the Galaxy project 
<https://github.com/ansible/galaxy/>.


Thanks!

Chris Houseknecht
Galaxy Team Manager
chousekn -at- redhat.com

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/494824e6-4a28-4cf5-a0eb-dc0cea8ee81c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy Outage Starting Friday, Feb 24 at 7:00 PM Eastern

[Chris Houseknecht]

Beginning Friday, Feb 24 at 7:00 PM Eastern we will be migrating Galaxy 
from its current hosting provider to EC2.

As a result of the migration, Galaxy will be down for a short period of 
time. We do not anticipate the outage lasting for more than one hour. 

Please watch the mailing list for updates.


--
Chris Houseknecht
Principal Engineer
Ansible by Red Hat 

*GitHub: *chouseknecht
<https://www.github.com/chouseknecht>*Twitter: *@chouseknecht 
<https://www.twitter.com/@chouseknecht>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/6d582f4a-3917-4498-8d47-b6522ddaa916%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy update tonight at 10:00 PM

[Chris Houseknecht]

Update completed. Automatic imports via Travis notifications should be 
working once again.

--Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/be24843f-79eb-43b0-9502-e91c42fff45a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy update tonight at 10:00 PM

[Chris Houseknecht]

We will be pushing an update to Galaxy this evening that fixes broken 
Travis notifications and automatic role imports. See issue 189 
 for details.

The update will be quick, and we do not anticipate any downtime. Will 
update the list after the deployment finishes.


--Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/b2ef2615-0c3e-4b39-8fbd-3e86cec02a30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy release 6:00 PM EDT today

[Chris Houseknecht]

Galaxy update completed.

On Monday, October 3, 2016 at 2:16:12 PM UTC-4, Chris Houseknecht wrote:
>
> We will be pushing an update to the Galaxy site 
> <https://galaxy.ansible.com> this evening starting at 6:00 PM EDT. 
>  Please be aware that although we don't anticipate any detectable outage, 
> it's entirely possible that something may brake during deployment.
>
> Will update the mailing list as soon as the update completes. 
>
> --Chris
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/99827238-d0dc-4994-86b7-36d027eb3a9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy release 6:00 PM EDT today

[Chris Houseknecht]

We will be pushing an update to the Galaxy site  
this evening starting at 6:00 PM EDT.  Please be aware that although we 
don't anticipate any detectable outage, it's entirely possible that 
something may brake during deployment.

Will update the mailing list as soon as the update completes. 

--Chris


-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/26cc6405-7935-448b-964d-42880cd9ccee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: How to use new Azure modules

[Chris Houseknecht]

This was definitely a problem, and it has been fixed in the devel branch 
with PR #16559 . To use this 
fix you will need to:

- Run from source 

 
- Install Azure Python SDK == 2.0.0rc5 


--Chris


On Sunday, May 29, 2016 at 11:02:00 AM UTC-4, Takeshi Kuramochi wrote:
>
> Hi All, 
>
> I would like to know details to use Azure modules ( azure_rm_xx ) 
> . because it failed tasks for azure. 
>
> I already have own azure account. 
> I think that I must get some objects ( ad_user / password ) on my 
> azure portal before I write a playbook. 
> I read below. 
>
> https://azure.microsoft.com/en-us/documentation/articles/automation-credentials/
>  
>
> I set ~/.azure/credentials then I run playbook. 
>
> --- 
> - name: VM image fact 
>   azure_rm_virtualmachineimage_facts: 
> location: eastus 
> publisher: OpenLogic 
> offer: CentOS 
> sku: '7.1' 
> version: '7.1.20160308' 
>
>
> It failed. 
>
> TASK [azure : VM image fact] 
> *** 
> task path: /home/vagrant/build_host/roles/azure/tasks/test.yml:1 
>  ESTABLISH LOCAL CONNECTION FOR USER: vagrant 
>  EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo 
> $HOME/.ansible/tmp/ansible-tmp-1464532575.87-18674131270164 `" && echo 
> ansible-tmp-1464532575.87-18674131270164="` echo 
> $HOME/.ansible/tmp/ansible-tmp-1464532575.87-18674131270164 `" ) && 
> sleep 0' 
>  PUT /tmp/tmpxJJVCb TO 
> /home/vagrant/.ansible/tmp/ansible-tmp-1464532575.87-18674131270164/azure_rm_virtualmachineimage_facts
>  
>
>  EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 
> LC_MESSAGES=en_US.UTF-8 /usr/bin/python 
> /home/vagrant/.ansible/tmp/ansible-tmp-1464532575.87-18674131270164/azure_rm_virtualmachineimage_facts;
>  
>
> rm -rf 
> "/home/vagrant/.ansible/tmp/ansible-tmp-1464532575.87-18674131270164/" 
> > /dev/null 2>&1 && sleep 0' 
> fatal: [localhost]: FAILED! => {"changed": false, "failed": true, 
> "invocation": {"module_name": "azure_rm_virtualmachineimage_facts"}, 
> "module_stderr": 
> "/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:315:
>  
>
> SNIMissingWarning: An HTTPS request has been made, but the SNI 
> (Subject Name Indication) extension to TLS is not available on this 
> platform. This may cause the server to present an incorrect TLS 
> certificate, which can cause validation failures. For more 
> information, see 
> https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.\n 
>
>  
> SNIMissingWarning\n/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:120:
>  
>
> InsecurePlatformWarning: A true SSLContext object is not available. 
> This prevents urllib3 from configuring SSL appropriately and may cause 
> certain SSL connections to fail. For more information, see 
>
> https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.\n
>  
>
>  InsecurePlatformWarning\nTraceback (most recent call last):\n  File 
> \"/tmp/ansible_pmEfA1/ansible_module_azure_rm_virtualmachineimage_facts.py\", 
>
> line 239, in \nmain()\n  File 
> \"/tmp/ansible_pmEfA1/ansible_module_azure_rm_virtualmachineimage_facts.py\", 
>
> line 236, in main\nAzureRMVirtualMachineImageFacts()\n  File 
> \"/tmp/ansible_pmEfA1/ansible_module_azure_rm_virtualmachineimage_facts.py\", 
>
> line 149, in __init__\nsuper(AzureRMVirtualMachineImageFacts, 
> self).__init__(self.module_arg_spec)\n  File 
> \"/tmp/ansible_pmEfA1/ansible_modlib.zip/ansible/module_utils/azure_rm_common.py\",
>  
>
> line 169, in __init__\n  File 
> \"/usr/local/lib/python2.7/dist-packages/msrestazure/azure_active_directory.py\",
>  
>
> line 261, in __init__\nself.set_token()\n  File 
> \"/usr/local/lib/python2.7/dist-packages/msrestazure/azure_active_directory.py\",
>  
>
> line 296, in set_token\nraise_with_traceback(AuthenticationError, 
> \"\", err)\n  File 
> \"/usr/local/lib/python2.7/dist-packages/msrest/exceptions.py\", line 
> 50, in raise_with_traceback\nraise 
> error\nmsrest.exceptions.AuthenticationError: , InvalidGrantError: 
> (invalid_grant) AADSTS50034: To sign into this application the account 
> must be added to the management.core.windows.net directory.\r\nTrace 
> ID: cc08968a-517f-4e8b-ac2e-09423825472c\r\nCorrelation ID: 
> 1bd9c2bf-8299-4455-88b1-de3eced3eb80\r\nTimestamp: 2016-05-29 
> 14:36:19Z\n", "module_stdout": "", "msg": "MODULE FAILURE", "parsed": 
> false} 
>
> PLAY RECAP 
> * 
> localhost  : ok=1changed=0unreachable=0   
>  failed=1 
>
> Maybe ~/.azure/credentials has problems, but I did not understand. 
>
> ~/.azure/credentials 
> subscription_id:  
> ad_user: xxx 
> password: xxx 
>
>
>
> Any and all help is appreciated! 
>

-- 
You 

[ansible-project] Re: Ansible docker module does not allow me to use bind mode :Z

[Chris Houseknecht]

The doc strings are in the docker.py module code: 
https://github.com/ansible/ansible-modules-core/blob/devel/cloud/docker/docker.py.
 
These doc strings are used to generate the documentation site page for the 
docker module: http://docs.ansible.com/ansible/docker_module.html. 

Ansible 2.1 has not actually been released. 2.1 is what is being worked on 
in the devel branch today. It is scheduled for release in April 
<https://github.com/ansible/ansible/blob/devel/ROADMAP.md>.  You can run 
the latest code by installing from source. See some help on how to do that 
here: 
http://docs.ansible.com/ansible/intro_installation.html#running-from-source


--Chris

On Thursday, March 3, 2016 at 1:33:13 AM UTC-5, ishan jain wrote:
>
> Thanks chris. Can you please share the links to this documentation ?
>
> Also, i was trying to find the Ansible version 2.1. Can you help me here 
> also ?
>
> On Tuesday, 1 March 2016 00:35:51 UTC+5:30, Chris Houseknecht wrote:
>>
>> What version of ansible are you running? 
>>
>> According to the doc strings in the docker.py module:
>>
>> volumes:
>>
>>   description:
>>
>> - List of volumes to mount within the container
>>
>> - 'Use docker CLI-style syntax: C(/host:/container[:mode])’
>>
>> - You can specify a read mode for the mount with either C(ro) or 
>> C(rw). Starting at version 2.1, SELinux hosts can 
>>
>>   additionally use C(z) or C(Z) mount options to use a shared or 
>> private label for the volume.
>>
>>
>> If I'm understanding the above correctly, options z and Z became 
>> available for SE Linux hosts in Ansible 2.1.
>>
>> Also, I wonder if the format of ` - /mydata/folder:/opt/mydata/:Z` might 
>> be incorrect? I would remove the last '/', changing it to ` - 
>> /mydata/folder:/opt/mydata:Z`
>>
>>
>>
>> --Chris
>>
>>
>> On Monday, February 29, 2016 at 6:29:35 AM UTC-5, ishan jain wrote:
>>>
>>> When i try to run the following task:
>>>
>>> - name: start docker container
>>>   docker:
>>> name: container
>>> image: img
>>> state: started
>>>expose:
>>>   - 8301:8182
>>>volumes:
>>>   - /mydata/folder:/opt/mydata/:Z
>>>
>>>
>>> Ansible poses an error - {"changed": false, "failed": true, "msg": "bind 
>>> mode needs to either be \"ro\" or \"rw\""}
>>>
>>> I was facing a lot of issues with volumes earlier when i was using :ro 
>>> (manual deployment) which went away after simply using :Z. Now ansible is 
>>> not letting me use it and the same images are posing errors when starting. 
>>> Can you please tell me why it is not allowed and how to come around this 
>>> thing ?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/2cf9d29e-185f-479e-8a67-1ab8aa4c0e4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Ansible docker module does not allow me to use bind mode :Z

[Chris Houseknecht]

What version of ansible are you running? 

According to the doc strings in the docker.py module:

volumes:

  description:

- List of volumes to mount within the container

- 'Use docker CLI-style syntax: C(/host:/container[:mode])’

- You can specify a read mode for the mount with either C(ro) or C(rw). 
Starting at version 2.1, SELinux hosts can 

  additionally use C(z) or C(Z) mount options to use a shared or 
private label for the volume.


If I'm understanding the above correctly, options z and Z became available 
for SE Linux hosts in Ansible 2.1.

Also, I wonder if the format of ` - /mydata/folder:/opt/mydata/:Z` might be 
incorrect? I would remove the last '/', changing it to ` - 
/mydata/folder:/opt/mydata:Z`



--Chris


On Monday, February 29, 2016 at 6:29:35 AM UTC-5, ishan jain wrote:
>
> When i try to run the following task:
>
> - name: start docker container
>   docker:
> name: container
> image: img
> state: started
>expose:
>   - 8301:8182
>volumes:
>   - /mydata/folder:/opt/mydata/:Z
>
>
> Ansible poses an error - {"changed": false, "failed": true, "msg": "bind 
> mode needs to either be \"ro\" or \"rw\""}
>
> I was facing a lot of issues with volumes earlier when i was using :ro 
> (manual deployment) which went away after simply using :Z. Now ansible is 
> not letting me use it and the same images are posing errors when starting. 
> Can you please tell me why it is not allowed and how to come around this 
> thing ?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/84df64d3-91da-4062-baae-ad9229dfcd22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy 2.0.1 Release

[Chris Houseknecht]

Galaxy upgrade completed. w00t!

--c

On Friday, February 26, 2016 at 10:36:16 AM UTC-5, Chris Houseknecht wrote:
>
> Smarter people than me pointed out that Monday morning would be better. 
> They may be right. Galaxy 2.0.1 will release Monday morning at 7:30AM EST. 
>
> --c
>
> On Friday, February 26, 2016 at 7:43:06 AM UTC-5, Chris Houseknecht wrote:
>>
>> False start. We're having some jenkins issues. Delaying until this 
>> evening at 6:00 PM EST.  Stay tuned!
>>
>>
>> --Chris
>>
>> On Friday, February 26, 2016 at 7:28:02 AM UTC-5, Chris Houseknecht wrote:
>>>
>>> Starting the upgrade...
>>>
>>> On Tuesday, February 23, 2016 at 12:54:57 PM UTC-5, Chris Houseknecht 
>>> wrote:
>>>>
>>>> We will be releasing Galaxy <https://galaxy.ansible.com/> 2.0.1 this 
>>>> Friday 2/26 starting at 7:30AM EST and ending at 8:00AM EST. During this 
>>>> window access to Galaxy may be interrupted, so please plan accordingly.
>>>>
>>>>
>>>> --Chris
>>>>
>>>>
>>>> Chris Houseknecht
>>>> Lead Galaxy Engineer
>>>> @chouseknecht <http://twitter.com/chouseknecht>
>>>> RedHat | Ansible <http://ansible.com/>
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c8f649cc-06a5-4bee-b006-f6843f2db11a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy 2.0.1 Release

[Chris Houseknecht]

Smarter people than me pointed out that Monday morning would be better. 
They may be right. Galaxy 2.0.1 will release Monday morning at 7:30AM EST. 

--c

On Friday, February 26, 2016 at 7:43:06 AM UTC-5, Chris Houseknecht wrote:
>
> False start. We're having some jenkins issues. Delaying until this evening 
> at 6:00 PM EST.  Stay tuned!
>
>
> --Chris
>
> On Friday, February 26, 2016 at 7:28:02 AM UTC-5, Chris Houseknecht wrote:
>>
>> Starting the upgrade...
>>
>> On Tuesday, February 23, 2016 at 12:54:57 PM UTC-5, Chris Houseknecht 
>> wrote:
>>>
>>> We will be releasing Galaxy <https://galaxy.ansible.com/> 2.0.1 this 
>>> Friday 2/26 starting at 7:30AM EST and ending at 8:00AM EST. During this 
>>> window access to Galaxy may be interrupted, so please plan accordingly.
>>>
>>>
>>> --Chris
>>>
>>>
>>> Chris Houseknecht
>>> Lead Galaxy Engineer
>>> @chouseknecht <http://twitter.com/chouseknecht>
>>> RedHat | Ansible <http://ansible.com/>
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/6f0b5ca0-3678-4789-8929-a864872745b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy - Install Role from Subdirectory of Github Repo

[Chris Houseknecht]

The role installation process does not support this at present.  We're in 
the middle of re-thinking how role installs work. If you're interested, 
there is a proposal at github.com/ansible/ansible. Look in docs/proposals.

Combining multiple roles into a single repo makes things like testing, 
linting and versioning more complicated, so I don't know that we really 
want to add this support. However, you can always suggest it and see what 
the community thinks. 

--Chris 


On Thursday, February 25, 2016 at 12:37:17 PM UTC-5, Nick Allen wrote:
>
>
> I have a Github repository that contains multiple roles, each in separate 
> subdirectories.  For example, I have separate roles 'role-alpha' and 
> 'role-beta' in a repo at https://github.com/whoami/project.git each 
> located in subdirectories as follows.
>
>- provisioning/roles/role-alpha
>- provisioning/roles/role-beta
>
>
> I am trying to install these roles via a 'requirements.yml' file by 
> running the following.
>
> ansible-galaxy install -r requirements.yml
>  
> Can I install roles from a single Github repository that have multiple 
> roles, each in unique subdirectories?  What would the definition look like?
>
> - name: role-alpha
>   src: https://github.com/whoami/project.git
>   ???: provisioning/roles/role-alpha
>
> Many thanks for any advice.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c80b5ebb-bcf1-4150-af6e-84e72318fe75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy 2.0.1 Release

[Chris Houseknecht]

False start. We're having some jenkins issues. Delaying until this evening 
at 6:00 PM EST.  Stay tuned!


--Chris

On Friday, February 26, 2016 at 7:28:02 AM UTC-5, Chris Houseknecht wrote:
>
> Starting the upgrade...
>
> On Tuesday, February 23, 2016 at 12:54:57 PM UTC-5, Chris Houseknecht 
> wrote:
>>
>> We will be releasing Galaxy <https://galaxy.ansible.com/> 2.0.1 this 
>> Friday 2/26 starting at 7:30AM EST and ending at 8:00AM EST. During this 
>> window access to Galaxy may be interrupted, so please plan accordingly.
>>
>>
>> --Chris
>>
>>
>> Chris Houseknecht
>> Lead Galaxy Engineer
>> @chouseknecht <http://twitter.com/chouseknecht>
>> RedHat | Ansible <http://ansible.com/>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/9af6f742-1555-429a-be8a-e65f491f6b28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy 2.0.1 Release

[Chris Houseknecht]

Starting the upgrade...

On Tuesday, February 23, 2016 at 12:54:57 PM UTC-5, Chris Houseknecht wrote:
>
> We will be releasing Galaxy <https://galaxy.ansible.com/> 2.0.1 this 
> Friday 2/26 starting at 7:30AM EST and ending at 8:00AM EST. During this 
> window access to Galaxy may be interrupted, so please plan accordingly.
>
>
> --Chris
>
>
> Chris Houseknecht
> Lead Galaxy Engineer
> @chouseknecht <http://twitter.com/chouseknecht>
> RedHat | Ansible <http://ansible.com/>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c911f210-bc5c-4c3a-8c75-66dccb3ee785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy Maintenance Window 2/25 7:30AM EST

[Chris Houseknecht]

And... we're back. Maintenance completed and Galaxy is up without any 
issues. 

--Chris

On Thursday, February 25, 2016 at 7:29:27 AM UTC-5, Chris Houseknecht wrote:
>
> Starting network maintenance...
>
> On Tuesday, February 23, 2016 at 12:50:14 PM UTC-5, Chris Houseknecht 
> wrote:
>>
>> We will be performing some network maintenance on Galaxy 
>> <https://galaxy.ansible.com> this Thursday 2/25 starting at 7:30AM EST 
>> and ending at 8:00AM EST. We will do our best to keep access to Galaxy 
>> uninterrupted during this window.
>>
>> --Chris
>>
>>
>> Chris Houseknecht
>> Lead Galaxy Engineer
>> @chouseknecht <http://twitter.com/chouseknecht>
>> RedHat | Ansible <http://ansible.com>
>>
>>   
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/46d879b2-e434-47cc-90d7-1e83b7a7a5aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy Maintenance Window 2/25 7:30AM EST

[Chris Houseknecht]

Starting network maintenance...

On Tuesday, February 23, 2016 at 12:50:14 PM UTC-5, Chris Houseknecht wrote:
>
> We will be performing some network maintenance on Galaxy 
> <https://galaxy.ansible.com> this Thursday 2/25 starting at 7:30AM EST 
> and ending at 8:00AM EST. We will do our best to keep access to Galaxy 
> uninterrupted during this window.
>
> --Chris
>
>
> Chris Houseknecht
> Lead Galaxy Engineer
> @chouseknecht <http://twitter.com/chouseknecht>
> RedHat | Ansible <http://ansible.com>
>
>   
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/c40fb652-c5dd-4fc4-8dc5-1c0d0f3f8c15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy 2.0.1 Release

[Chris Houseknecht]

We will be releasing Galaxy <https://galaxy.ansible.com/> 2.0.1 this Friday 
2/26 starting at 7:30AM EST and ending at 8:00AM EST. During this window 
access to Galaxy may be interrupted, so please plan accordingly.


--Chris


Chris Houseknecht
Lead Galaxy Engineer
@chouseknecht <http://twitter.com/chouseknecht>
RedHat | Ansible <http://ansible.com/>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/5ac6571b-fa73-4d84-9143-dc4fa79ef57e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy Maintenance Window 2/25 7:30AM EST

[Chris Houseknecht]

We will be performing some network maintenance on Galaxy 
<https://galaxy.ansible.com> this Thursday 2/25 starting at 7:30AM EST and 
ending at 8:00AM EST. We will do our best to keep access to Galaxy 
uninterrupted during this window.

--Chris


Chris Houseknecht
Lead Galaxy Engineer
@chouseknecht <http://twitter.com/chouseknecht>
RedHat | Ansible <http://ansible.com>

  

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/93b5ea10-496a-4b7b-983d-57f6509e9fe6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: galaxy import: "Waiting to start..."

[Chris Houseknecht]

The task runner was restarted and imports are working again. 

--chris


On Wednesday, February 17, 2016 at 11:29:03 AM UTC, Roger Gomez wrote:
>
> I'm still experiencing this issue, any idea when is going to be resolved.
>
> On Wednesday, February 10, 2016 at 8:38:03 AM UTC-5, nusenu wrote:
>>
>> Hi, 
>>
>> an hour after importing a new role [1] it still says: 
>>
>> Waiting to start..." 
>> in "View Role Import Details". 
>>
>> How long does it usually take to import a role? 
>>
>> thanks! 
>>
>>
>> [1] nusenu/ansible-relayor 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3ee78d2c-9a63-4e24-9591-5dfdc2e44baf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: galaxy import status: waiting to start

[Chris Houseknecht]

Looks like your role imported.  I assume this is it: 
 https://galaxy.ansible.com/rvichery/nuage-vsc-installer/

We had some problems with the import process overnight, but they have been 
resolved.  I've been monitoring and imports are working as expected. The 
import should (and is currently) starting almost immediately. 

If you see that the import process is taking an inordinate amount of time 
to get started, please open an issue at Galaxy Issues 
<https://github.com/ansible/galaxy-issues>.  And please know, that we are 
working to improve the stability of the import process (see issue #113 
<https://github.com/ansible/galaxy-issues/issues/113>). New code and config 
changes should (fingers crossed) make it into production with the 2.0.1 
release on 2/26. 

Chris Houseknecht
@chouseknecht
Lead Galaxy Engineer
RedHat | Ansible



On Wednesday, February 17, 2016 at 11:29:03 AM UTC, Rémi Vichery wrote:
>
> Hello,
>
> I tried to import a new role  (nuage-vsc-installer)  in galaxy some 
> minutes ago but the status is still "waiting to start". When I try to 
> access the role I receive a 404 error.
>
> How long does it take to import the role ?
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/826d9892-378e-4711-a2c8-ef699642ac25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Docker Modules Roadmap

[Chris Houseknecht]

We’re excited to announce a clear roadmap to providing first-class support 
for container orchestration with Ansible. Over the coming months we will 
create a supported and maintainable solution that keeps pace with the fast 
moving world of containers.

The current Docker modules will be around for a while yet, but as the new 
container modules begin to take shape, we will deprecate the current 
modules.

To kick things off we identified a list of core modules Ansible must 
provide. The list appears below with a description of the module’s purpose 
and scope.

But before we get too far down the development path, we need to hear from 
you. We’ll be thinking and collaborating on the shape of each module here: 

https://public.etherpad-mozilla.org/p/9RQPFWC1Mv

Have a look at the list of modules. Tells us what we missed. What could be 
better? We’ll take your input and shape the roadmap between now and 2/26 
before officially kicking off development.



Thanks!


Chris Houseknecht

@chouseknecht <https://twitter.com/chouseknecht>

RedHat | Ansible <http://ansible.com/>



Core Docker Modules

docker_container

Manage the container lifecycle through created, started, stopped, killed, 
paused and unpaused states. Development of this module will start with the 
current docker module and remove things falling outside of this scope. 
Functionality that can be shared by all modules will be moved to 
module_utils.

docker_files

Provide an interface to the docker cp and diff API endpoints.

docker_image

Manage docker images using the build, list, pull, push, rmi, tag, and save 
image API endpoints. Development will begin with the current docker_image 
module.  

docker_network

Manage docker networks through the network connect, create, disconnect, 
inspect, ls and rm endpoints.

docker_volume

Manage docker volumes through the volume create, inspect, ls and rm API 
endpoints.

docker_login

An interface to the login API endpoint. Development will begin with the 
current docker_login module.

docker_daemon

Manage the docker daemon through the docker daemon API endpoint.


docker inventory script

Develop an inventory script that provides comprehensive docker container 
facts and can connect to either a locally running or remote API.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/470942df-774f-4044-bd0c-f87893ad63f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: galaxy vs. Ubuntu 15.10

[Chris Houseknecht]

As taken from meta/main.yml created using `ansible-galaxy init` after 
Ubuntu Wily was added:

#- name: Ubuntu
  #  versions:
  #  - all
  #  - lucid
  #  - maverick
  #  - natty
  #  - oneiric
  #  - precise
  #  - quantal
  #  - raring
  #  - saucy
  #  - trusty
  #  - utopic
  #  - vivid
  #  - wily


Ubuntu releases are by name rather than version, so you'll want to use 
'wily'.


On Thursday, February 11, 2016 at 4:02:04 AM UTC-5, nusenu wrote:
>
>
>
> Chris Houseknecht: 
> > Task runner infrastructure upgraded. Hopefully we'll see better 
> > performance. 
>
> thanks. 
>
> > Added Ubuntu Wily. 
>
> Does one has to use the codename?  "15.10" does not seem to work still. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/985fc1c1-58dd-4d34-963d-1ccec031599d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy maintenance tonight 10 PM EST

[Chris Houseknecht]

This evening starting at 10:00PM EST and ending at 11:00PM EST the galaxy 
task system will be upgraded. During this maintenance window Galaxy may 
experience a service interruption.


--Chris



Chris Houseknecht 
@chouseknecht
Lead Galaxy Engineer
RedHat | Ansible

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a5c69e2c-09a3-4863-88db-5c6ae114ddc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: galaxy import: "Waiting to start..."

[Chris Houseknecht]

The task runner that handles imports has been restarted and the task queue 
cleared. If you click the 're-import' button now, it should now start right 
away. We're having some challenges with the task runner and planning to 
make some adjustments this evening.

--Chris



On Wednesday, February 10, 2016 at 8:38:03 AM UTC-5, nusenu wrote:
>
> Hi, 
>
> an hour after importing a new role [1] it still says: 
>
> Waiting to start..." 
> in "View Role Import Details". 
>
> How long does it usually take to import a role? 
>
> thanks! 
>
>
> [1] nusenu/ansible-relayor 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/78c846fd-ed65-4024-b627-34fbedd238f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: galaxy: reame formatting problems

[Chris Houseknecht]

GitHub's markdown is a little more forgiving than Galaxy. Galaxy stores the 
raw README and translates to HTML on request. Galaxy also has its own CSS 
styles, so by definition what you see on Galaxy will be a little different. 

We have been doing some work on the Galaxy styling of README files. Those 
changes will appear in release 2.0.1 scheduled to land on 2/26.

With the above in mind, if you indent sub-lists by 4 spaces, you should get 
the lists to appear the way you want. GitHub supports 2 spaces, where 
markdown proper requires 4. In the Requirements section, separate lists 
from paragraphs with a blank line. And finally, at the bottom of your 
README there is a numbered list, make sure each bullet has the correct 
number.

I forked your role, made the above minor changes and imported into our QA 
environment. You can see it here: 
https://galaxy-qa.ansible.com/chouseknecht/relayor/

--Chris  



On Wednesday, February 10, 2016 at 11:01:00 AM UTC-5, nusenu wrote:
>
> Hi, 
>
> there seems to be a problem with galaxy displaying READMEs, see: 
>
> https://galaxy.ansible.com/nusenu/relayor/ 
>
> vs 
>
> https://github.com/nusenu/ansible-relayor 
>
>
> especially the sections: 
> Requirements 
> Available Role Tags 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/75877988-741d-4a8e-a10a-79dd8fa938a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Why does galaxy need write access to github repositories?

[Chris Houseknecht]

Galaxy asks for the following scopes used to access the GitHub API:

- user:email
- public_repo
- read:org

These are defined here: https://developer.github.com/v3/oauth/#scopes

The last two allow us to see the orgs you belong to and the repos you have 
access to, which is needed when building the list of role repositories on 
My Roles page.


--Chris




On Wednesday, February 10, 2016 at 12:05:13 PM UTC-5, nusenu wrote:
>
> Hi, 
>
> when logging in into galaxy.ansible.com, 
> galaxy asks for write access to repositories, why is that? 
>
> Is it possible to have a role on galaxy without giving galaxy write 
> access to github repositories? 
>
> thanks, 
> nusenu 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/6288bdfe-1988-45fc-80c1-9b1e43fff277%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy maintenance tonight 10 PM EST

[Chris Houseknecht]

Galaxy maintenance was completed and all should be stable.

--Chris

On Wednesday, February 10, 2016 at 10:54:23 AM UTC-5, Chris Houseknecht 
wrote:
>
> This evening starting at 10:00PM EST and ending at 11:00PM EST the galaxy 
> task system will be upgraded. During this maintenance window Galaxy may 
> experience a service interruption.
>
>
> --Chris
>
>
>
> Chris Houseknecht 
> @chouseknecht
> Lead Galaxy Engineer
> RedHat | Ansible
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/357a1a08-86a8-41e0-afa4-8c9248648823%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: galaxy import: "Waiting to start..."

[Chris Houseknecht]

Task runner infrastructure upgraded. Hopefully we'll see better 
performance. 

Added Ubuntu Wily. 

--c

On Wednesday, February 10, 2016 at 2:53:17 PM UTC-5, nusenu wrote:
>
>
> > Chris Houseknecht: 
> >> The task runner that handles imports has been restarted and the task 
> queue 
> >> cleared. If you click the 're-import' button now, it should now start 
> right 
> >> away. We're having some challenges with the task runner and planning to 
> >> make some adjustments this evening. 
> > 
>
> Yes, looks like it is stuck again. 
> I fixed the README file but now: 
> "Waiting to start..." 
> looking forward to 10PM ;) 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/bcb76cf8-1f52-49d0-b8a1-3105067cfd44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Deploying Galaxy 2.0

[Chris Houseknecht]

Starting the deployment of Galaxy 2.0. There may be a small service 
interruption between 6:10 and 6:30AM EST this morning.

--Chris


Chris Houseknecht
@chouseknecht
Lead Galaxy Engineer
RedHat | Ansible

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3dd2f512-b56c-4e4a-9429-fdd0fe272b24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Deploying Galaxy 2.0

[Chris Houseknecht]

Galaxy 2.0 is live.

Please report any issues at https://github.com/ansible/galaxy-issues.

--Chris

On Wednesday, January 27, 2016 at 6:09:42 AM UTC-5, Chris Houseknecht wrote:
>
> Starting the deployment of Galaxy 2.0. There may be a small service 
> interruption between 6:10 and 6:30AM EST this morning.
>
> --Chris
>
>
> Chris Houseknecht
> @chouseknecht
> Lead Galaxy Engineer
> RedHat | Ansible
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3fffa5bd-81b0-463f-b84c-bb99d3331ec6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible-galaxy with http/s proxy

[Chris Houseknecht]

Submitted PR https://github.com/ansible/ansible/pull/13808 to add 
--ignore-certs option to init, install and info commands in ansible-galaxy 
1.9.4.

--Chris

On Monday, January 11, 2016 at 4:40:03 PM UTC-5, Chris Houseknecht wrote:
>
> This works in ansible 2.0. It requires using the --ignore-certs flag. 
>
> I simulated a proxy server using Charles Proxy. In the Charles proxy 
> settings I enabled SSL Proxying for galaxy.ansible.com:443. Then I did 
> the following:
>
> $ export https_proxy=http://localhost:
> $ ansible-galaxy --ignore-certs init my-role-foo
> - my-role-foo was created successfully
>
> From the above I can see the request route through Charles and return a 
> valid response from the API. Without --ignore-certs the init command fails. 
> I think the issue is that the proxy is not forwarding the root certificate 
> from galaxy.ansible.com down to the client.
>
> Prior to 2.0 the --ignore-certs flag is not available on the init command. 
> I'm looking into the code now and will submit a PR to add it.
>
>
> --Chris
>
>
>
> On Monday, January 11, 2016 at 11:00:57 AM UTC-5, Jameson Pugh wrote:
>>
>> On Sunday, January 10, 2016 at 2:15:37 AM UTC-5, Александр Костырев wrote:
>>>
>>> I've got the same problem.
>>>
>>
>> I'm also running into this issue. I have http_proxy and https_proxy 
>> variables pointing to our proxy server, and I'm able to wget and curl from 
>> galaxy.ansible.com, but if I run ansible-galaxy init, I get "- the API 
>> server (galaxy.ansible.com) is not responding, please try again later." 
>> Is the only way I'll be able to use it at this point manually downloading? 
>> Thanks.
>>
>> =-Jameson
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/efa23761-d04a-45a8-96c9-c7b65070b988%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible-galaxy with http/s proxy

[Chris Houseknecht]

This works in ansible 2.0. It requires using the --ignore-certs flag. 

I simulated a proxy server using Charles Proxy. In the Charles proxy 
settings I enabled SSL Proxying for galaxy.ansible.com:443. Then I did the 
following:

$ export https_proxy=http://localhost:
$ ansible-galaxy --ignore-certs init my-role-foo
- my-role-foo was created successfully

>From the above I can see the request route through Charles and return a 
valid response from the API. Without --ignore-certs the init command fails. 
I think the issue is that the proxy is not forwarding the root certificate 
from galaxy.ansible.com down to the client.

Prior to 2.0 the --ignore-certs flag is not available on the init command. 
I'm looking into the code now and will submit a PR to add it.


--Chris



On Monday, January 11, 2016 at 11:00:57 AM UTC-5, Jameson Pugh wrote:
>
> On Sunday, January 10, 2016 at 2:15:37 AM UTC-5, Александр Костырев wrote:
>>
>> I've got the same problem.
>>
>
> I'm also running into this issue. I have http_proxy and https_proxy 
> variables pointing to our proxy server, and I'm able to wget and curl from 
> galaxy.ansible.com, but if I run ansible-galaxy init, I get "- the API 
> server (galaxy.ansible.com) is not responding, please try again later." 
> Is the only way I'll be able to use it at this point manually downloading? 
> Thanks.
>
> =-Jameson
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/83f25b9d-3d12-41d8-979d-8b6ead25e0be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy 2.0 Beta now available

[Chris Houseknecht]

See  http://www.ansible.com/blog/galaxy-2.0-beta for details.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/1069cd3e-4e3c-40a6-ab28-610c44b68fd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Ansible galaxy repo import

[Chris Houseknecht]

It looks like the import process does not like the tag 'new-relic' found in 
meta/main.yml.  Tags should only contain alphanumeric characters.

It should just skip over the tag and continue importing the role, so there 
is a bug in that regard. For now, please try removing 'new-relic' and 
re-importing the role.  

--Chris


On Monday, November 30, 2015 at 2:52:44 PM UTC-5, Adithya Khamithkar wrote:
>
> Hi,
>
> My role seems to be taking a very long time to import from github to 
> galaxy. I have the right syntax in the meta file. Can someone please let me 
> know what could be the reason for it taking such a long time to import?
>
> Thanks,
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/d182b83f-c1f1-40ee-87b4-f6ce4a035b48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy 1.1.1 release

[Chris Houseknecht]

Galaxy  1.1.1 is live.

--Chris

On Thursday, October 29, 2015 at 4:40:21 PM UTC-4, Chris Houseknecht wrote:
>
> We will be releasing Galaxy 1.1.1 tomorrow at 8:00 AM EDT.  This a small 
> maintenance release addressing a handful of minor bugs. There will be no 
> interruption of service during the deployment. 
>
> The complete list of bug fixes included in release 1.1.1 can be found 
> here. 
> <https://github.com/ansible/galaxy-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.1.1>
>
>
>
> Chris Houseknecht
> Lead Galaxy Engineer
> chouseknecht at ansible.com
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/4dfde956-47c8-4e4a-bf56-5fdc4709b94e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy 1.1.1 release

[Chris Houseknecht]

We will be releasing Galaxy 1.1.1 tomorrow at 8:00 AM EDT.  This a small 
maintenance release addressing a handful of minor bugs. There will be no 
interruption of service during the deployment. 

The complete list of bug fixes included in release 1.1.1 can be found here. 
<https://github.com/ansible/galaxy-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.1.1>



Chris Houseknecht
Lead Galaxy Engineer
chouseknecht at ansible.com


-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/27c781b8-d265-4c3e-a694-283ba66fc1c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy maintenance tomorrow @ 8:30AM EDT

[Chris Houseknecht]

Starting the upgrade.  Will post again when we're done. 

--Chris

On Wednesday, October 21, 2015 at 8:30:19 AM UTC-4, Chris Houseknecht wrote:
>
> Between 8:30AM and 9:00 AM EDT tomorrow we will be upgrading the Galaxy 
> infrastructure and releasing Galaxy 1.1. Expect Galaxy access to be 
> interrupted during this window. 
>
> We will update the mailing list as soon as the upgrade is complete and 
> Galaxy is back online.
>
> Apologies for any inconvenience.
>
>
> Chris Houseknecht
> Lead Galaxy Engineer
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/2754ab18-08dd-46c2-8cbd-a2a8054eea87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Galaxy maintenance tomorrow @ 8:30AM EDT

[Chris Houseknecht]

Upgrade completed. w00t!  Welcome to Galaxy 1.1 <https://galaxy.ansible.com>

--Chris

On Thursday, October 22, 2015 at 8:31:59 AM UTC-4, Chris Houseknecht wrote:
>
> Starting the upgrade.  Will post again when we're done. 
>
> --Chris
>
> On Wednesday, October 21, 2015 at 8:30:19 AM UTC-4, Chris Houseknecht 
> wrote:
>>
>> Between 8:30AM and 9:00 AM EDT tomorrow we will be upgrading the Galaxy 
>> infrastructure and releasing Galaxy 1.1. Expect Galaxy access to be 
>> interrupted during this window. 
>>
>> We will update the mailing list as soon as the upgrade is complete and 
>> Galaxy is back online.
>>
>> Apologies for any inconvenience.
>>
>>
>> Chris Houseknecht
>> Lead Galaxy Engineer
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/80e9563d-5eb2-4639-aba7-9d3014fde82c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Galaxy maintenance tomorrow @ 8:30AM EDT

[Chris Houseknecht]

Between 8:30AM and 9:00 AM EDT tomorrow we will be upgrading the Galaxy 
infrastructure and releasing Galaxy 1.1. Expect Galaxy access to be 
interrupted during this window. 

We will update the mailing list as soon as the upgrade is complete and 
Galaxy is back online.

Apologies for any inconvenience.


Chris Houseknecht
Lead Galaxy Engineer

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/ec2d13ea-0161-4837-b92b-bad0b326ad8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] ansible-galaxy - replacing Categories with Tags

[Chris Houseknecht]

In our next release of Galaxy (hopefully later this week) we will deprecate 
Categories in favor of Tags.  Role authors can add tags or keywords that 
best describe and categorize their role. Users of Galaxy will be able to 
search by tags. 

Submitted PR 12456  to 
modify ansible-galaxy cli to reflect this change.  It modifies the metadata 
template by removing categories and adding an empty tags array with 
instructions.  And for the search command it replaces the --categories 
option with a --tags option.

The PR also adds --ignore-certs option to the install and search commands. 
This works nicely when --server is used to point to a host with a self 
signed cert. 


-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/67ec4d2e-573a-4321-aef3-561f64e39b97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: Adding new Galaxy role fails every time...

[Chris Houseknecht]

Hey Chris-

Noticed also that `dependencies:` is defined incorrectly in your 
meta/main.yml.  It needs to be an array.  

Change line 107 to:

dependencies: []



And, I believe that should fix the import issue.

I've added code to the Galaxy import process to surface this error on the 
UI. The change will land in our next release.  Apologies for the 
inconvenience.  Let me know, if you still run into issues. 


Chris Houseknecht
chouse at ansible.com




On Friday, September 11, 2015 at 1:44:58 PM UTC-4, Christopher Mancini 
wrote:
>
> Hello, I attempted to add a role to Ansible Galaxy, but no matter what I 
> try, it fails to import. I think its not saving the data properly. Here are 
> the details.
>
> Repository: https://github.com/basho-labs/ansible-riak
>
> Input to 'Add a Role' form:
> GH User: basho-labs
> GH Repo: ansible-riak
> alt name: riak-kv
>
> resulting role: https://galaxy.ansible.com/list#/roles/5077
>
> GH Repo button on above page links to https://github.com//
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/4d131ff1-5669-4e51-b0e2-47eef43bfd4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Adding new Galaxy role fails every time...

[Chris Houseknecht]

Hey Chris-

Looks like there is an issue with `dependencies:` in meta/main.yml.  It 
should be an array.

Change line 107 in meta/main.yml to:

dependencies: []


And that should do it. 

I added code to surface this error to the Galaxy UI.  The change will land 
in our next release.  Apologies for any inconvenience.  If it still doesn't 
work, please feel free to reach out to me. 

Chris Houseknecht
chouse at ansible.com


On Sunday, September 13, 2015 at 8:17:38 PM UTC-4, Christopher Mancini 
wrote:
>
> Thanks Bill. I removed the two non-ascii apostrophe's I found, pushed the 
> changes up and hit re-import, it has been running for like an hour and has 
> only updated the keywords. It seems to be stuck. Should I delete and re-add?
>
> On Friday, September 11, 2015 at 1:58:58 PM UTC-4, Bill Nottingham wrote:
>>
>> It's a known issue with parsing the Unicode characters in the README.md 
>> file. We're working to fix that in Galaxy, but if you swap out the 
>> apostrophes for the ASCII equivalent, it should work.
>>
>> Bill
>>
>>
>> On Fri, Sep 11, 2015 at 1:15 PM, Christopher Mancini <manc...@gmail.com> 
>> wrote:
>>
>>> Hello, I attempted to add a role to Ansible Galaxy, but no matter what I 
>>> try, it fails to import. I think its not saving the data properly. Here are 
>>> the details.
>>>
>>> Repository: https://github.com/basho-labs/ansible-riak
>>>
>>> Input to 'Add a Role' form:
>>> GH User: basho-labs
>>> GH Repo: ansible-riak
>>> alt name: riak-kv
>>>
>>> resulting role: https://galaxy.ansible.com/list#/roles/5077
>>>
>>> GH Repo button on above page links to https://github.com//
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to ansible-proje...@googlegroups.com.
>>> To post to this group, send email to ansible...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ansible-project/1decd42d-d3b6-4225-a562-67876e63c521%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/ansible-project/1decd42d-d3b6-4225-a562-67876e63c521%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Bill Nottingham
>> Director of Product, Ansible
>> ansible.com
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3c1643cc-c8bf-489c-a764-8a6d2167e8cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.