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

e/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 fro

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

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-

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

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 --

[ansible-project] Deploying Galaxy 2.0

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 "An

[ansible-project] Re: Deploying Galaxy 2.0

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

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

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

[ansible-project] Galaxy maintenance tonight 10 PM EST

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

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

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. T

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

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

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

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 t

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

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 wind

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

# - 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 >

[ansible-project] Docker Modules Roadmap

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, star

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

(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 a

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

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: >> >>

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

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 En

[ansible-project] Galaxy 2.0.1 Release

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

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

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 w

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

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

[ansible-project] Re: Galaxy 2.0.1 Release

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

[ansible-project] Re: Galaxy 2.0.1 Release

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,

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

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, lin

[ansible-project] Re: Galaxy 2.0.1 Release

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. Del

[ansible-project] Re: Galaxy 2.0.1 Release

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. > > --

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

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 eith

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

e > 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: >> &

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

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

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

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

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

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 anticipat

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

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

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

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-p

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

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 "Ansib

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

. 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

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

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 t

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

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

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

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 po

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

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 Galax

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

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, 20

[ansible-project] Galaxy 1.1.1 release

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

[ansible-project] Re: Galaxy 1.1.1 release

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 se

[ansible-project] Re: Ansible galaxy repo import

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-impor

[ansible-project] Galaxy 2.0 Beta now available

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

[ansible-project] Re: ansible-galaxy github-token calling non-existant API endpoint

The doc site is not up to speed with the latest in the stable-2.0 branch. If it were, you would see a note explaining the following: Note > The login command in Ansible 2.0 requires using the Galaxy 2.0 Beta site. > Use the --server option to access https://galaxy-qa.ansible.com. You can > also