Hello Infra,
When I try to send my code to review.opwnstack.org I get an error:
$ git review
fatal: ICLA contributor agreement requires current contact information.
Please review your contact information:
https://review.openstack.org/#/settings/contact
fatal: Could not read from remote repos
On 08/01/2016 02:50 PM, Dmitry Dmitriev wrote:
> Hello Infra,
>
> When I try to send my code to review.opwnstack.org I get an error:
>
> $ git review
> fatal: ICLA contributor agreement requires current contact information.
>
> Please review your contact information:
>
> https://review.opensta
How about something like a playbook that runs on puppetmaster periodically
doing something like this:
create_server_translate_a
create_server_translate_b
set_dns
The create_server_translate tasks would be idempotent, i.e. they won't leak
servers.
The set DNS task would check a file on the puppetm
On 2016-08-01 16:08:49 +0200 (+0200), Ricardo Carrillo Cruz wrote:
[...]
> The set DNS task would check a file on the puppetmaster which contains the
> state of blue/green DNS records (translate-latest.openstack.org pointing to
> translate_a and translate-soon-to-be-deleted.openstack.org pointing t
In my mind, I thought set_dns would be really an ansible wrapper to
system-config launch/dns.py script.
But yeah, putting the switch on what's Devstack latest and what's not on an
Apache reverse proxy works too.
The workflow would be similar to what I depicted.
I think the biggest issue is that D
On 2016-08-01 16:46:07 +0200 (+0200), Ricardo Carrillo Cruz wrote:
> In my mind, I thought set_dns would be really an ansible wrapper to
> system-config launch/dns.py script.
[...]
There's a reason why that script only tells you what commands to
run, and doesn't run them for you. At least that way
Oh, hahaha, I thought the dns.py was actually doing something.
Now that I see the script I know what you mean :-).
2016-08-01 17:10 GMT+02:00 Jeremy Stanley :
> On 2016-08-01 16:46:07 +0200 (+0200), Ricardo Carrillo Cruz wrote:
> > In my mind, I thought set_dns would be really an ansible wrapper
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday August 2nd, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
Anyone is welcome to to add agenda i
Hi,
We finally got out code in. However, we are seeing that even though the
code is present in https://git.openstack.org/openstack/python-don, it has
not yet been mirrored to https://github.com/openstack/python-don. Do we
need to do anything to trigger the mirroring?
Regards,
Amit
On Wed, Jul 27
Am 2016-07-25 19:05, schrieb Jeremy Stanley:
On 2016-07-25 11:08:35 +0530 (+0530), Vipul Nayyar wrote:
Honestly, I was also thinking that using containers for implementing
blue/green deployment would be best for implementing minimal downtime.
I
suggest having a basic run-through of this idea wi
On 2016-08-01 19:26:07 +0200 (+0200), Frank Kloeker wrote:
> broken DevStack installation - that's the point. With LXD
> container you can take snapshot, run unstack or clean script,
> fetch new code and stack again. If it failed you can restore the
> snapshot and try new installation on another da
On 2016-08-01 22:31:37 +0530 (+0530), Amit Saha wrote:
> We finally got out code in. However, we are seeing that even though the
> code is present in https://git.openstack.org/openstack/python-don, it has
> not yet been mirrored to https://github.com/openstack/python-don. Do we
> need to do anythin
12 matches
Mail list logo
