Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

personally see this proposal helping us with Edge use cases in a meaningful way given the scope of the changes. That's not to say there aren't other use cases that could justify it though (such as the security points brought up ea

[openstack-dev] [TripleO] Edge squad meeting this week and next week

I won't be around to run the Edge squad meeting this week and next week. If someone else wants to pick it up, that would be great. Otherwise, consider it cancelled :). Thanks! https://etherpad.openstack.org/p/tripleo-edge-squad-status -- -- James Slagle

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

ly cosmetic, but using free does create a lot more noisier output IMO. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

uality and I think he would > be a addition to the core team. > > What do you folks think? +1 -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-d

Re: [openstack-dev] [TripleO] easily identifying how services are configured

d hopefully reduce the amount of time it takes to create/update the ServiceChain stacks. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?s

[openstack-dev] [TripleO] Chair for Edge squad meeting this week

I won't be able to chair the edge squad meeting this week. Can anyone take it over? If not, we'll pick it back up next week. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

[openstack-dev] [TripleO] Edge Squad meeting

, please bring them up. See everyone for the meeting. Thanks! -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [TripleO] Plan management refactoring for Life cycle

customed to devops type workflows. I think we could make these changes without it impact the API too much or, hopefully, at all. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

On Mon, Aug 20, 2018 at 4:47 PM James Slagle wrote: > https://etherpad.openstack.org/p/tripleo-edge-squad-status Several folks have signed up for the squad, so I've added a poll in the etherpad to pick a meeting time. > -- > -- James Slagle > -- -- --

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

l add something to the etherpad. Thanks. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

esday with the group. https://etherpad.openstack.org/p/EdgeComputingGroupPTG4 -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.o

[openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

facilitate the squad. If you have any feedback on these ideas or would like to join the squad, reply to the thread or sign up in the etherpad: https://etherpad.openstack.org/p/tripleo-edge-squad-status I'm just referring to the squad as "Edge" for now, but we can also pick a cooler owl

Re: [openstack-dev] [tripleo] network isolation can't find files referred to on director

On Thu, Jul 26, 2018 at 4:58 AM, Samuel Monderer wrote: > Hi James, > > I understand the network-environment.yaml will also be generated. > What do you mean by rendered path? Will it be > "usr/share/openstack-tripleo-heat-templates/network/ports/"? Yes, the rendered path is the path that the

Re: [openstack-dev] [tripleo] network isolation can't find files referred to on director

See: https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/custom_networks.html -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openst

Re: [openstack-dev] [tripleo] prototype with standalone mode and remote edge compute nodes

us quickly answer these questions and develop a "Steel Thread"[1] to build upon. Ultimately, this is the sort of high level designs and architectures we are beginning to investigate. We are trying to let the use cases and operator need address the design, even while the use

Re: [openstack-dev] [tripleo] prototype with standalone mode and remote edge compute nodes

at I've been testing with split-controlplane: https://review.openstack.org/#/c/521928/ https://review.openstack.org/#/c/521929/ https://review.openstack.org/#/c/581080/ I'll pull some docs together if I have some initial success. -- -- James Slagle -- __

Re: [openstack-dev] [TripleO] easily identifying how services are configured

umes the default? Or perhaps a symlink, although it was pointed out symlinks don't work in swift containers. Still, that could possibly be addressed in our plan upload workflows. Then the resource-registry would point at nova-api-default.yaml.

Re: [openstack-dev] [TripleO] config-download/ansible next steps

could support the existing method forever for upgrades, and only deprecate it for new deployments. I'd like to help with this work. I'll start by taking a look at what you've got so far. Feel free to reach out if you'd like some additional dev assistance or testing. -- -- James Slagle --

[openstack-dev] [TripleO] config-download/ansible next steps

/openstack/tripleo-specs/specs/rocky/split-controlplane.html -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tripleo] scenario000-multinode-oooq-container-upgrades

On Tue, Jun 12, 2018 at 11:03 AM, Jiří Stránský wrote: > On 12.6.2018 15:06, James Slagle wrote: >> >> On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin >> wrote: >>> >>> Greetings, >>> >>> I wanted to let everyone know that we have a

Re: [openstack-dev] [tripleo] scenario000-multinode-oooq-container-upgrades

es: http://logs.openstack.org/59/571459/1/check/tripleo-ci-centos-7-scenario000-multinode-oooq-container-upgrades/8bbd827/logs/undercloud/home/zuul/overcloud_upgrade_run_Controller.log.txt.gz Is this a known issue? -- -- James Slagle -- _

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

I wonder how many people will care to > follow it though. Yes, this sounds pretty reasonable to me. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On Thu, Apr 26, 2018 at 10:24 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: > Answering to both James and Ben inline. > > > On 04/25/2018 05:47 PM, Ben Nemec wrote: >> >> >> >> On 04/25/2018 10:28 AM, James Slagle wrote: >>> >>

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur <dtant...@redhat.com> wrote: > On 04/25/2018 04:26 PM, James Slagle wrote: >> >> On Wed, Apr 25, 2018 at 9:14 AM, Dmitry Tantsur <dtant...@redhat.com> >> wrote: >>> >>> Hi all, >>> >

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

s. And even that was not enabled by default. IMO, we need to keep "safe" defaults. Even if it means manually documenting that you should clean to prevent the issues you point out above. The alternative is to have no way to recover deleted nodes by default. -- -- James Slagle --

Re: [openstack-dev] [tripleo] Proposing Marius Cornea core on upgrade bits

her tripleo repos for the patches > related to upgrades (we trust people's judgement for reviews). > > As usual, we'll vote! > > Thanks everyone for your feedback and thanks Marius for your hard work and > in

Re: [openstack-dev] [TripleO][ci][ceph] switching to config-download by default

On Thu, Apr 5, 2018 at 10:38 AM, James Slagle <james.sla...@gmail.com> wrote: > I've pushed up for review a set of patches to switch us over to using > config-download by default: > > https://review.openstack.org/#/q/topic:bp/config-download-default > > I believe I've

Re: [openstack-dev] [TripleO][ci][ceph] switching to config-download by default

On Thu, Apr 5, 2018 at 10:38 AM, James Slagle <james.sla...@gmail.com> wrote: > I've pushed up for review a set of patches to switch us over to using > config-download by default: > > https://review.openstack.org/#/q/topic:bp/config-download-default > > I believe I've

[openstack-dev] [TripleO][ci][ceph] switching to config-download by default

. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

download playbooks for any given TripleO stack (openstack tripleo depoy?). This would be possible when using deployed-server, noop'ing Neutron networks, and using fixed IP's as those are the only OpenStack resources actually created by Heat when using a full undercloud. This would allow one to con

[openstack-dev] [TripleO] ansible/config-download PTG session recap

the default by the Rocky-1 milestone (April 16 - April 20), and I feel we're still on track to do that. If you'd like to help with this effort we're coordinating our work with this etherpad: https://etherpad.openstack.org/p/tripleo-config-download-squad-status -- -- James Slagle

[openstack-dev] [TripleO] Deep dive on Ansible Integration Thursday Feb 22 1400UTC

://bluejeans.com/7754237859/ Optional pre-reading: https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/ansible_config_download.html The session will be recorded and later uploaded to Youtube at: https://www.youtube.com/channel/UCNGDxZGwUELpgaBoLvABsTA -- -- James Slagle

Re: [openstack-dev] [tripleo] Updates on containerized undercloud

m for the routed ctlplane work that landed at the end of Queens. Afaik, that will need to be supported with the containerized undercloud. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) U

[openstack-dev] [TripleO][ui] config-download (ansible deployment) by default in Rocky

status. I'll set this up this week. If you plan to participate with this work, please let me know. [1] https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/ansible_config_download.html -- -- James Slagle

Re: [openstack-dev] [TripleO][CI] Which network templates to use in CI (with and without net isolation)?

into tripleo-heat-templates. Otherwise, why do we need them there are at all? -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

re team > (tripleo-ci, t-q and t-q-e repos for now). > Anyway, thanks a lot Wes for your hard work on CI, I think it's time > to move on and get you +2 ;-) > > As usual, it's open for voting, feel free to bring any fe

Re: [openstack-dev] [TripleO] Proposing Ronelle Landy for Tripleo-Quickstart/Extras/CI core

importantly has always > done quality reviews. She also has been working in the very intense rover > role on the CI squad in the past CI sprint, and has done very well in that > role. +1 -- -- James Slagle -- __ OpenS

Re: [openstack-dev] [TripleO] IPSEC integration

tly also consuming. You may find that is an easier way of consuming the standalone Ansible roles you've already done as opposed to trying to make those fit into the composable services framework that uses t-h-t in tree Ansible tasks. -- -- James Slagle -- __

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

On Fri, Nov 17, 2017 at 4:43 AM, Steven Hardy <sha...@redhat.com> wrote: > On Thu, Nov 16, 2017 at 4:56 PM, James Slagle <james.sla...@gmail.com> wrote: >> On Thu, Nov 16, 2017 at 8:44 AM, Flavio Percoco <fla...@redhat.com> wrote: >> What I'm trying to prop

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

and then finally perhaps no Heat[1]. [0] https://slagle.fedorapeople.org/tripleo-ansible-arch.png [1] Except for perhaps deployment of baremetal resources, but even then I'm personally of the opinion that would be better serviced by Mistral

Re: [openstack-dev] [TripleO] Next steps for pre-deployment workflows (e.g derive parameters)

On Wed, Nov 8, 2017 at 7:16 AM, James Slagle <james.sla...@gmail.com> wrote: > On Wed, Nov 8, 2017 at 12:09 AM, Steven Hardy <sha...@redhat.com> wrote: >> Hi all, >> >> Today I had a productive hallway discussion with jtomasek and >> stevebaker re

Re: [openstack-dev] [TripleO] Next steps for pre-deployment workflows (e.g derive parameters)

stral as part of the deployment. Right now, we have no such requirement, and are able to drive a deployment with only an ephemeral Heat and ansible-playbook, which is the basis of how undercloud deploy works. -- -- James Slagle -- __

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

oud, using the new ansible installer. I also want to keep > running Tempest. > And of course, like we said, keep one multinode job to test overcloud > workflow, and OVB with some adjustments. > > Is i

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

test less upstream so that we can more quickly merge code, then *not* deploying an overcloud in the gate at all seems to fit that goal. Is that what you're after? -- -- James Slagle -- __ OpenStack Development Mailing List (not

Re: [openstack-dev] [TripleO] Deployment workflow changes for ui/client

If we're happy with where we get to in queens with config-download, we could consider making it the default. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstac

[openstack-dev] [TripleO] Deployment workflow changes for ui/client

ble-config-download -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailma

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Thu, Sep 21, 2017 at 11:53 AM, Jiří Stránský <ji...@redhat.com> wrote: > On 21.9.2017 18:04, Marios Andreou wrote: >> >> On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský <ji...@redhat.com> wrote: >> >>> On 21.9.2017 12:31, Giulio Fidente wrote: >>&

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente <gfide...@redhat.com> wrote: > On 09/18/2017 05:37 PM, James Slagle wrote: >> - The entire sequence and flow is driven via Mistral on the Undercloud >> by default. This preserves the API layer and provides a clean reusable >

Re: [openstack-dev] [puppet] - No way to pass extra variables from a heat template to a puppet manifest

gt; HugePageCount: 4 > > > ​Since you're setting use_hiera:True in the config, there should be a hieradata file created for the config under /etc/puppet/hieradata on the node(s) associated with the deployment. That hiera file should automatically be included whenever you run pu

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

a variety of eventual solutions that can interface with playbooks (Mistral, AWX, cli, etc). I don't imagine we'd do anything prohibitive that would prevent someone from loading those playbooks into AWX if desired, or using them directly from the cli. You just wouldn't be going through the official API

[openstack-dev] [TripleO] TripleO/Ansible PTG session

still be considered open for discussion. [1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html [2] https://slagle.fedorapeople.org/tripleo-ansible-arch.png -- -- James Slagle -- __ OpenStack Deve

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Mon, Jul 24, 2017 at 3:12 AM, Marios Andreou <mandr...@redhat.com> wrote: > > > On Fri, Jul 21, 2017 at 1:21 AM, James Slagle <james.sla...@gmail.com> > wrote: >> >> Following up on the previous thread: >> http://lists.openstack.org/pipermail/openstac

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 9:52 PM, James Slagle <james.sla...@gmail.com> wrote: > On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger <pabelan...@redhat.com> wrote: >> On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: >>> Following up on the previous thread:

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger <pabelan...@redhat.com> wrote: > On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: >> Following up on the previous thread: >> http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html >> >>

[openstack-dev] [TripleO] An experiment with Ansible

plates. Although I'm not trying to say it'd be a small amount of work to even do that, as this is a very rough prototype. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

ving to use OpenStack (OVB, split-stack). That's exactly why we are starting a discussion around using Ansible, and is one of the fundamental changes that operators have been requesting in TripleO. -- -- James Slagle -- __ Op

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Fri, Jul 14, 2017 at 3:38 PM, Steven Dake <steven.d...@gmail.com> wrote: > > > On Fri, Jul 14, 2017 at 10:26 AM, James Slagle <james.sla...@gmail.com> > wrote: >> > James, > >> >> Just to frame the conversation with a bit more context, I'm sure th

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

elm I still see room for collaboration on code beneath the Helm/whatever layer. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker <sba...@redhat.com> wrote: > > > On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman <l...@redhat.com> > wrote: >> >> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle <james.sla...@gmail.com> >> wrote:

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker <sba...@redhat.com> wrote: > > > On Tue, Jul 11, 2017 at 6:51 AM, James Slagle <james.sla...@gmail.com> > wrote: >> >> On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman <l...@redhat.com> >> wrote: &

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente <gfide...@redhat.com> wrote: > On 07/10/2017 07:06 PM, James Slagle wrote: >> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente <gfide...@redhat.com> wrote: >>> splitstack though requires changes in how the *ex

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman <l...@redhat.com> wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle <james.sla...@gmail.com> wrote: >> >> There are also some ideas forming around pulling the Ansible playbooks >> >> and vars out of

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente <gfide...@redhat.com> wrote: > On 07/10/2017 03:19 PM, Steven Hardy wrote: >> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle <james.sla...@gmail.com> wrote: > > [...] > >> Yeah, I think the first step is to foc

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 9:19 AM, Steven Hardy <sha...@redhat.com> wrote: > On Fri, Jul 7, 2017 at 6:50 PM, James Slagle <james.sla...@gmail.com> wrote: > Yeah so my idea with (4), and subsequent patches such as[1] is to > gradually move the deploy steps performed

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

; As usual, this is an open proposal, any feedback is welcome. +1 -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 5:31 PM, David Moreau Simard <d...@redhat.com> wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle <james.sla...@gmail.com> wrote: >> (0) tripleo-quickstart which follows the common and well accepted >> approach to bundling a set of Ansible p

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

least offer some form of migration tooling. Thanks for your feedback. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu

[openstack-dev] [TripleO] Forming our plans around Ansible

like to collaborate around that. I think if we can form some broad agreement before the PTG, we have a chance at making some meaningful progress during Queens. -- -- James Slagle -- __ OpenStack Development Mailing List (not

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 20)

gt; There are a couple of jobs that is still not transitioned running on a few > repos. We need to figure out if those jobs are still needed and if yes, > what's holding them back from transition. Hi, is there a plan or potential dates for tra

Re: [openstack-dev] [TripleO] Deep dive Thursday May 4th 1400 UTC on deployed-server

On Wed, May 3, 2017 at 8:34 AM, James Slagle <james.sla...@gmail.com> wrote: > I saw there was no deep dive scheduled for tomorrow, so I decided I'd > go ahead and plan one. > > It will be recorded if you can't make it on the short notice. > > I plan to cover the &

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

ents in those choices instead of making comments such as what you've done here. While minor (with some thinly veiled praise sprinkled in), I'm a bit shocked no one else has called attention to your response. It is not friendly, considerate, and above all else -- it is not respectful.

[openstack-dev] [TripleO] Deep dive Thursday May 4th 1400 UTC on deployed-server

end to end "split-stack". Thursday May 4th at 1400 UTC at https://bluejeans.com/176756457/ You don't want to miss it! (or maybe you do). Go Owls! -- -- James Slagle -- __ OpenStack Development Mailing List (not

Re: [openstack-dev] [tripleo] Idempotence of the deployment process

ho know what they're doing, actually be able to do it". There are risks with exposing more knobs to enable/disable functionality. However, if you know what you're doing, and it's documented sufficiently, then there are huge benefits as well (e.g., huge reduction in

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

instance a week or so ago. I think it's all due to development environments. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On Wed, Mar 8, 2017 at 4:08 AM, Steven Hardy <sha...@redhat.com> wrote: > On Tue, Mar 07, 2017 at 02:34:50PM -0500, James Slagle wrote: >> I've been working on this spec for TripleO: >> https://review.openstack.org/#/c/431745/ >> >> which allows users to se

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On Tue, Mar 7, 2017 at 7:24 PM, Zane Bitter <zbit...@redhat.com> wrote: > On 07/03/17 14:34, James Slagle wrote: >> >> I've been working on this spec for TripleO: >> https://review.openstack.org/#/c/431745/ >> >> which allows users to selectively disable H

[openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

, is Heat interested in this functionality natively? I think it would make for a much cleaner implementation than something TripleO specific. I can work on a Heat spec if there's interest, though I'd like to get some early feedback. Thanks. -- -- James Slagle

[openstack-dev] [TripleO] Spinning up multinode environments using Heat

in this branch: https://review.openstack.org/#/q/topic:traas Any feedback is welcome. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

nd committers to tripleo-docs. I wouldn't be opposed to him having +2 there as well. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu

Re: [openstack-dev] [tripleo] Update TripleO core members

; - Add Flavio Percoco core on tripleo-common and tripleo-heat-templates > docker bits. > - Add Steve Backer on os-collect-config and also docker bits in > tripleo-common and tripleo-heat-templates. +1 -- -- James Slagle --

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

TripleO CI core team. > > I think he'll make a great addition to the team and will help move CI > issues forward quicker. +1 -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Un

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

made in governance however. The reason I -1'd Paul's TripleO spec and suggested it be proposed to diskimage-builder was due to: http://lists.openstack.org/pipermail/openstack-dev/2016-June/098560.html and https://review.openstack.org/#/c/336109/ I just want to make sure the right set of reviewers

Re: [openstack-dev] [tripleo] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

system, especially around release time. I'm wondering if there are still plans to move to 3rd party and how those plans might line up with this proposed schedule. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105248.html -- -- James Slagle -- __

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

Alex for your involvement and hard work in the project, this is > very appreciated! > > As usual, I'll let the team to vote about this proposal. +1 -- -- James Slagle -- __ OpenStack Development Mailing List (not

Re: [openstack-dev] [TripleO] Proposing Julie Pichon for tripleo core

en get enough attention (backports, bug triaging/reporting and improving > our processes[2]). > > I think she will be a valuable addition to the review team +1 -- -- James Slagle -- __ OpenStack Development Ma

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

an ability to branch out and dive into any aspect of TripleO. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [TripleO] Newton release this week

://review.openstack.org/#/c/391799/ -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] [tripleo] Ocata specs

Given we reviewed all the blueprints at the summit, and discussed all the features we plan to implement for Ocata, I think it would be reasonable to go with the above. However, 'm interested in any feedback or if anyone feels that requiring a blueprin

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

jobs are a natural fit for 3rd party CI. So, I feel like more naturally aligning our CI efforts with the reset of the infra community is the most reasonable path to make significant forward progress that can scale our CI and improve how quickly the core team ca

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

ub.com/openstack-infra/tripleo-ci/blob/master/test-environments/worker-config.yaml. If we can get that down to 1, looks like that might save around 270MB. It also looks like there are 2 nova-api workers despite having NovaWorkers: 1. Is that normal? Getting rid of on

Re: [openstack-dev] [infra][tripleo] status of tripleo-test-cloud-rh1

On Mon, Aug 8, 2016 at 1:47 PM, James Slagle <james.sla...@gmail.com> wrote: > On Mon, Aug 8, 2016 at 1:06 PM, Jeremy Stanley <fu...@yuggoth.org> wrote: >> On 2016-08-08 11:47:56 -0400 (-0400), James Slagle wrote: >> [...] >>> I suppose it's also possible t

Re: [openstack-dev] [TripleO] TripleO Core nominations

und networking in future. > > Please can I get feedback from exisitng core reviewers - you're free to +1 > these nominations (or abstain), but any -1 will veto the process. I'll > wait one week, and if we have consensus add the above folks to > tripleo-core. +1 to all. -- -- James S

Re: [openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

https://review.openstack.org/#/q/topic:mistral-validations If I missed anything, please point it out. -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstac

Re: [openstack-dev] [TripleO][CI] Need more undercloud resources

On Thu, Aug 25, 2016 at 9:49 AM, James Slagle <james.sla...@gmail.com> wrote: > On Thu, Aug 25, 2016 at 5:40 AM, Derek Higgins <der...@redhat.com> wrote: >> On 25 August 2016 at 02:56, Paul Belanger <pabelan...@redhat.com> wrote: >>> On Wed, Aug 24, 2016 at

Re: [openstack-dev] [tripleo] Barcelona Design Summit space needs

ation and see if that can be accommodated. > > What do folks think, if I can get some acks on this plan I will go ahead > and provide the feedback to Thierry. +1, sounds good to me. -- -- James Slagle -- __ OpenStack

Re: [openstack-dev] [TripleO][CI] Need more undercloud resources

On Wed, Aug 24, 2016 at 9:56 PM, Paul Belanger wrote: > I actually believe these problem highlights how large tripleo-ci has grown, > and > in need of a refactor. While we won't solve this problem today, I do think > tripleo-ci is to monolithic today. I believe there is

Re: [openstack-dev] [TripleO][CI] Need more undercloud resources

On Thu, Aug 25, 2016 at 5:40 AM, Derek Higgins <der...@redhat.com> wrote: > On 25 August 2016 at 02:56, Paul Belanger <pabelan...@redhat.com> wrote: >> On Wed, Aug 24, 2016 at 02:11:32PM -0400, James Slagle wrote: >>> The latest recurring problem that is failing a

Re: [openstack-dev] [TripleO] TripleO Deep dive sessions for CI topics.

ot going to be the case given other constraints. It often comes down to what one is able to reproduce locally, and how to mitigate the issues as best we can (see email I just sent for an example). Let me know or add the specifics to the etherpad and I'll pull something together

[openstack-dev] [TripleO][CI] Need more undercloud resources

ent on making these changes. If there isn't, I'll apply them in the next day or so. If there are any other ideas on how to address this particular bug for some immediate short term relief, please let me know. -- -- James Sla

[openstack-dev] [TripleO] No Deep Dive this week

Thanks! -- -- James Slagle -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo

  1   2   3   >