Re: [openstack-dev] [TripleO] Python 3 support in os-*-config

Great stuff, really happy to see Python 3 support. - Original Message - From: Steve Kowalik ste...@wedontsleep.org To: openstack-dev@lists.openstack.org Sent: Friday, 15 August, 2014 4:11:04 AM Subject: [openstack-dev] [TripleO] Python 3 support in os-*-config * os-apply-config

Re: [openstack-dev] [TripleO] Change of meeting time

- Original Message - From: Derek Higgins der...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Wednesday, 20 August, 2014 10:15:51 AM Subject: Re: [openstack-dev] [TripleO] Change of meeting time On 24/05/14

Re: [openstack-dev] [TripleO][Tuskar] Domain Model Locations

I'm glad we are hashing this out as I think there is still some debate around if Tuskar will need a database at all. One thing to bear in mind, I think we need to make sure the terminology matches that described in the previous thread. I think it mostly does here but I'm not sure the Tuskar

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Hi, Thanks for the wireframes and the walkthrough. Very useful. I've a few comments. - I'd like to echo the comments from the recording about Role I think the term probably isn't specific enough but I don't have a great suggestion. However, this is probably suited better to the other

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

On 13/01/14 10:37, Jaromir Coufal wrote: So what we can do at the moment (until there is some way to specify which node to remove) is to inform user, which nodes were removed in the end... at least. Sounds like a good compromise for now. I think we probably then need feedback from

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

On 21/01/14 14:19, Jaromir Coufal wrote: when I was getting feedback on wireframes and we talked about Roles, there were various objections and not much suggestions. I would love to call for action and think a bit about the term for concept currently known as Role (= Resource Category). This

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

On 22/01/14 14:31, Tzu-Mainn Chen wrote: On 2014/22/01 10:00, Jaromir Coufal wrote: On 2014/22/01 00:56, Tzu-Mainn Chen wrote: Hiya - Resource is actually a Heat term that corresponds to what we're deploying within the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 19/02/14 17:10, Ladislav Smola wrote: Hello, I would like to have your opinion about how to deal with passwords in Tuskar-API The background is, that tuskarAPI is storing heat template parameters in its database, it's a preparation for more complex workflows, when we will need to store the

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 19/02/14 18:29, Jason Rist wrote: Would it be possible to create some token for use throughout? Forgive my naivete. I don't think so, the token would need to be understood by all the services that we store passwords for. I may be misunderstanding however. Dougal

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 19/02/14 18:49, Hugh O. Brock wrote: On Wed, Feb 19, 2014 at 06:31:47PM +, Dougal Matthews wrote: On 19/02/14 18:29, Jason Rist wrote: Would it be possible to create some token for use throughout? Forgive my naivete. I don't think so, the token would need to be understood by all

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 20/02/14 09:12, Radomir Dopieralski wrote: If we do need to store passwords it becomes a somewhat thorny issue, how does Tuskar know what a password is? If this is flagged up by the UI/client then we are relying on the user to tell us which isn't wise. All the template parameters that are

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 20/02/14 10:36, Radomir Dopieralski wrote: On 20/02/14 11:21, Dougal Matthews wrote: If we do store passwords however, I wonder if we are best to encrypt everything to be safe. The overhead shouldn't be that big and it may be better than special casing the NoEcho values. I think

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 21/02/14 09:24, Tomas Sedovic wrote: On 20/02/14 16:24, Imre Farkas wrote: On 02/20/2014 03:57 PM, Tomas Sedovic wrote: On 20/02/14 15:41, Radomir Dopieralski wrote: On 20/02/14 15:00, Tomas Sedovic wrote: Are we even sure we need to store the passwords in the first place? All this

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 21/02/14 10:03, Radomir Dopieralski wrote: On 21/02/14 10:38, Dougal Matthews wrote: At the moment we are guessing, we don't even know how many passwords we need to store. So we should progress with the safest and simplest option (which is to not store them) and consider changing this later

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On 26/02/14 18:38, Petr Blaho wrote: I am wondering what is the OpenStack way of returning json from apiclient. Good question, I think its important for us to be as consistent as possible. By looking at API docs at http://api.openstack.org/ I can say that projects use both ways, altought

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On 26/02/14 19:17, Jay Dobies wrote: This is a new concept to me in JSON, I've never heard of a wrapper element like that being called a namespace. It's certainly not in the spec AFAIK, but I've seen this approach before in various places. My first impression is that is looks like cruft. If

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26/02/14 19:43, Jay Dobies wrote: * Even at this level, it exposes the underlying guts. There are calls to nova baremetal listed in there, but eventually those will turn into ironic calls. It doesn't give us a ton of flexibility in terms of underlying technology if that knowledge bubbles up

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26/02/14 13:34, Jiří Stránský wrote: Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 This is great, thanks for taking the time to put it together. Another thing to add to my list of

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 27/02/14 15:08, Ladislav Smola wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will

Re: [openstack-dev] [TripleO] [Horizon] Searching for a new name for Tuskar UI

On 27/03/14 15:56, Jaromir Coufal wrote: Hi OpenStackers, User interface which is managing the OpenStack Infrastructure is currently named Tuskar-UI because of historical reasons. Tuskar itself is a small service, which is giving logic into generating and managing Heat templates and helps user

Re: [openstack-dev] [TripleO] [Horizon] Searching for a new name for Tuskar UI

On 27/03/14 18:11, Jay Dobies wrote: It might be good to do a similar thing as Keystone does. We could keep python-tuskarclient focused only on Python bindings for Tuskar (but keep whatever CLI we already implemented there, for backwards compatibility), and implement CLI as a plugin to

Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

On my phone so I can't follow this up more now, but it looks like JSHint is already used. https://review.openstack.org/#/c/41087/___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [tripleo] /bin/bash vs. /bin/sh

Another +1 for using bash. Sounds like an easy win. On 15/04/14 12:31, Ghe Rivero wrote: +1 to use bash as the default shell. So far, all major distros use bash as the default one (except Debian which uses dash). An about rewriting the code in Python, I agree that shell is complicated for large

Re: [openstack-dev] [TripleO] Change of meeting time

- Original Message - From: James Polley j...@jamezpolley.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Saturday, 24 May, 2014 1:21:53 AM Subject: [openstack-dev] [TripleO] Change of meeting time Following a lengthy

Re: [openstack-dev] [tripleO] Should #tuskar business be conducted in the #tripleo channel?

- Original Message - From: Jaromir Coufal jcou...@redhat.com To: openstack-dev@lists.openstack.org Sent: Friday, 30 May, 2014 12:04:29 PM Subject: Re: [openstack-dev] [tripleO] Should #tuskar business be conducted in the #tripleo channel? I'd say yes. I don't think the additional

Re: [openstack-dev] [Cinder][TripleO] Last days to elect your PTL!

Are the commits to Tuskar or Tuskar UI? Tuskar is under the tripleo project group but Tuskar UI is under Horizon IIRC. On Fri, Oct 3, 2014 at 8:22 PM, John Griffith john.griff...@solidfire.com wrote: On Fri, Oct 3, 2014 at 1:14 PM, Jason Rist jr...@redhat.com wrote: On 10/01/2014 08:22 PM,

Re: [openstack-dev] [TripleO] Alternate meeting time

- Original Message - From: James Polley j...@jamezpolley.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Thursday, 4 December, 2014 9:40:36 AM Subject: Re: [openstack-dev] [TripleO] Alternate meeting time Just taking a

Re: [openstack-dev] [TripleO][Tuskar] Common library for shared code

- Original Message - From: Jan Provazník jprov...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Monday, 9 March, 2015 8:35:29 PM Subject: [openstack-dev] [TripleO][Tuskar] Common library for shared code Hi, it

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

- Original Message - From: Zane Bitter zbit...@redhat.com To: OpenStack Development Mailing List openstack-dev@lists.openstack.org Sent: Monday, 17 August, 2015 5:25:36 PM Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the client It occurs to me that

Re: [openstack-dev] [TripleO] Moving instack upstream

- Original Message - From: Dmitry Tantsur dtant...@redhat.com To: openstack-dev@lists.openstack.org Sent: Wednesday, 19 August, 2015 5:57:36 PM Subject: Re: [openstack-dev] [TripleO] Moving instack upstream On 08/19/2015 06:42 PM, Derek Higgins wrote: On 06/08/15 15:01, Dougal

Re: [openstack-dev] [TripleO] Moving instack upstream

12:22 PM, Dougal Matthews wrote: - Original Message - From: Dmitry Tantsur dtant...@redhat.com To: openstack-dev@lists.openstack.org Sent: Wednesday, 19 August, 2015 5:57:36 PM Subject: Re: [openstack-dev] [TripleO] Moving instack upstream On 08/19/2015 06:42 PM

Re: [openstack-dev] [TripleO] Moving instack upstream

- Original Message - From: Dan Prince dpri...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Thursday, 6 August, 2015 1:12:42 PM Subject: Re: [openstack-dev] [TripleO] Moving instack upstream On Thu, 2015-07-23

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 9 November 2015 at 12:44, Dmitry Tantsur wrote: > Hi OOO'ers, hopefully the subject caught your attentions :) > > Currently, tripleoclient exposes several commands in "openstack baremetal" > and "openstack baremetal introspection" namespaces belonging to ironic and >

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 10 November 2015 at 15:08, Tzu-Mainn Chen wrote: > Hi all, > > At the last IRC meeting it was agreed that the new TripleO REST API > should forgo the Tuskar name, and simply be called... the TripleO > API. There's one more point of discussion: where should the API >

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 10 November 2015 at 16:12, Giulio Fidente wrote: > On 11/10/2015 04:47 PM, Dmitry Tantsur wrote: > >> On 11/10/2015 04:37 PM, Giulio Fidente wrote: >> >>> On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: >>> On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: > Hi

Re: [openstack-dev] [TripleO] review priorities etherpad

On 13 October 2015 at 08:32, marios wrote: > On 10/10/15 00:16, Dan Prince wrote: > > On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > >> At the TripleO meething this week, we talked about using an etherpad > > speaking of which - and given attendance since the time

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

- Original Message - From: Jay Dobies jason.dob...@redhat.com To: openstack-dev@lists.openstack.org Sent: Tuesday, 25 August, 2015 2:31:02 PM Subject: Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client Thinking about this further, the interesting question

Re: [openstack-dev] [TripleO] Encapsulating logic and state in the client

- Original Message - From: Zane Bitter zbit...@redhat.com To: OpenStack Development Mailing List openstack-dev@lists.openstack.org Sent: Monday, 17 August, 2015 5:25:36 PM Subject: [openstack-dev] [TripleO] Encapsulating logic and state in the client It occurs to me that

[openstack-dev] [TripleO] Releasing tripleo-common on PyPI

Hi, The tripleo-common library appears to be registered or PyPI but hasn't yet had a release[1]. I am not familiar with the release process - what do we need to do to make sure it is regularly released with other TripleO packages? We will also want to do something similar with the new

[openstack-dev] [TripleO] Remove Tuskar from tripleo-common and python-tripleoclient

Hi all, This is partly a heads up for everyone, but also seeking feedback on the direction. We are starting to move to a more general Heat workflow without the need for Tuskar. The CLI is already in a position to do this as we can successfully deploy without Tuskar. Moving forward it will be

[openstack-dev] [TripleO] Defining a public API for tripleo-common

Hi, What is the standard practice for defining public API's for OpenStack libraries? As I am working on refactoring and updating tripleo-common I have to grep through the projects I know that use it to make sure I don't break anything. Personally I would choose to have a policy of "If it is

Re: [openstack-dev] [TripleO] Remove Tuskar from tripleo-common and python-tripleoclient

On 15 September 2015 at 17:33, Dougal Matthews <dou...@redhat.com> wrote: > [snip] > > [2]: https://review.openstack.org/223527 > [3]: https://review.openstack.org/223535 > [4]: https://review.openstack.org/223605 > For anyone interested in reviewing this work, the abo

Re: [openstack-dev] [puppet] [tripleo] stop maintaining puppet-tuskar

On 2 December 2015 at 16:38, Emilien Macchi wrote: > Hi, > > I don't find any official statement on the Internet, but I've heard > Tuskar is not going to be maintained anymore (tell me if I'm wrong). > I was hoping to raise this question at the TripleO meeting this week. The

Re: [openstack-dev] [TripleO] workflow

On 7 December 2015 at 14:59, Dan Prince <dpri...@redhat.com> wrote: > > > > On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > > > On 23 November 2015 at 14:37, Dan Prince <dpri...@redhat.com&

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: >>>> >>>>> On 12/23/2015 03:19 AM, Dougal Matthews wrote: >>>>> >>>>>> >>>>>> On 22 December 2015 at 17:59, Ben Nemec <openst...@nemebean.com >>>&g

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 6 January 2016 at 12:30, Ryan Brown <rybr...@redhat.com> wrote: > On 12/23/2015 04:19 AM, Dougal Matthews wrote: > >> >> >> On 22 December 2015 at 17:59, Ben Nemec <openst...@nemebean.com >> <mailto:openst...@nemebean.com>> wrote: >> &

[openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Hi all, This topic came up in the 2015-12-15 meeting[1], and again briefly today. After working with the code that came out of the deployment library spec[2] I had some concerns with how we are storing the templates. Simply put, when we are dealing with 100+ files from tripleo-heat-templates how

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 23 December 2015 at 12:01, Steven Hardy <sha...@redhat.com> wrote: > On Tue, Dec 22, 2015 at 03:36:02PM +0000, Dougal Matthews wrote: > >Hi all, > > > >This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > >After

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 23 December 2015 at 12:01, Steven Hardy <sha...@redhat.com> wrote: > On Tue, Dec 22, 2015 at 03:36:02PM +0000, Dougal Matthews wrote: > >Hi all, > > > >This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > >After

[openstack-dev] [TripleO] Removing the Tuskar repos

Hi all, I mentioned this at the meeting last week, but wanted to get wider input. As far as I can tell from the current activity, there is no work going into Tuskar and it isn't being tested with CI. This means the code is becoming more stale quickly and likely wont work soon (if not already).

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 16:56, Clint Byrum wrote: > Excerpts from Dougal Matthews's message of 2015-12-22 07:36:02 -0800: > > Hi all, > > > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > > After working with the code that came out of the deployment

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 18:50, Julien Danjou <jul...@danjou.info> wrote: > On Tue, Dec 22 2015, Dougal Matthews wrote: > > > - Store the files in a tarball (so we only deal with one file). I think > we > >could still hit issues with multiple operations unless we g

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 17:59, Ben Nemec <openst...@nemebean.com> wrote: > Can we just do git like I've been suggesting all along? ;-) > > More serious discussion inline. :-) > > On 12/22/2015 09:36 AM, Dougal Matthews wrote: > > Hi all, > > > > This to

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 19:29, Dan Prince <dpri...@redhat.com> wrote: > On Tue, 2015-12-22 at 15:36 +0000, Dougal Matthews wrote: > > Hi all, > > > > This topic came up in the 2015-12-15 meeting[1], and again briefly > > today. > > After working with t

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 17 November 2015 at 15:31, Tzu-Mainn Chen wrote: > > -- > > > > On 10 November 2015 at 15:08, Tzu-Mainn Chen wrote: > >> Hi all, >> >> At the last IRC meeting it was agreed that the new TripleO REST API >> should forgo the

Re: [openstack-dev] [TripleO] workflow

On 23 November 2015 at 14:37, Dan Prince wrote: > There are lots of references to "workflow" within TripleO conversations > these days. We are at (or near) the limit of what we can do within Heat > with regards to upgrades. We've got a new TripleO API in the works (a > new

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 24 November 2015 at 07:45, Richard Su wrote: > > > On 11/17/2015 07:31 AM, Tzu-Mainn Chen wrote: > > > -- > > > > On 10 November 2015 at 15:08, Tzu-Mainn Chen < > tzuma...@redhat.com> wrote: > >> Hi all, >> >> At the last IRC

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

On 9 June 2016 at 15:03, Steven Hardy wrote: > Hi all, > > I've been in discussion with Martin André and Tomas Sedovic, who are > involved with the creation of the new tripleo-validations repo[1] > > We've agreed that rather than create another gerrit group, they can be >

Re: [openstack-dev] [mistral] Team meeting reminder - 05/30/2016

On 30 May 2016 at 08:40, Renat Akhmerov wrote: > Hi, > > This is a reminder about the team meeting that we’ll have today at 16.00 > UTC at #openstack-meeting. > > Agenda: > >- Review action items >- Current status (progress, issues, roadblocks, further plans) >

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 22 June 2016 at 06:35, Renat Akhmerov wrote: > Hi, > > We’d like to finally come up with a logo for Mistral and it’d be cool to > hear some ideas from the community. > > Some ideas from me: > • A picture of a graph (but the point is that it must be very very

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On 27 January 2016 at 16:21, Derek Higgins wrote: > Hi All, > > We briefly discussed feature tracking in this weeks tripleo meeting. I > would like to provide a way for downstream consumers (and ourselves) to > track new features as they get implemented. The main things that

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

On 28 February 2016 at 22:41, Steve Baker <sba...@redhat.com> wrote: > On 27/02/16 09:06, Ben Nemec wrote: > >> Interesting! So this could conceivably be another consumer of the API, >> right? A sort of CLI UI? >> >> On 02/25/2016 01:10 PM, Dougal Matthew

[openstack-dev] [TripleO] Show TripleO: A terminal dashboard

Hi all, Over the past couple of weeks in my spare time I put together a basic Python urwid dashboard for TripleO. You can see the usage and some screenshots here: http://python-tripleodash.readthedocs.org The project is in very early stages (read as: very limited and buggy), but I've found it

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

ce to switch between it and working on the CLI (compared with switching to a browser). It has the advantage of being relatively easy to write as it has access to the environment and Python clients. > > On 02/25/2016 01:10 PM, Dougal Matthews wrote: > > Hi all, > > > > Over

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

; > right? A sort of CLI UI? > > > > On 02/25/2016 01:10 PM, Dougal Matthews wrote: > >> Hi all, > >> > >> Over the past couple of weeks in my spare time I put together a basic > >> Python urwid dashboard for TripleO. You can see the usage and

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 21 January 2016 at 14:46, Dougal Matthews <dou...@redhat.com> wrote: > > > On 20 January 2016 at 20:05, Tzu-Mainn Chen <tzuma...@redhat.com> wrote: > >> - Original Message - >> > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: >> > >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: > - Original Message - > > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > > - Original Message - > > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > >>> > > >>> - Original Message - > >

Re: [openstack-dev] [TripleO] Removing the Tuskar repos

On 22 December 2015 at 11:38, Dougal Matthews <dou...@redhat.com> wrote: > Hi all, > > I mentioned this at the meeting last week, but wanted to get wider input. > As far as I can tell from the current activity, there is no work going into > Tuskar and it isn't being teste

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 20 January 2016 at 10:03, Jiří Stránský wrote: > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > >> - Original Message - >> >>> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: >>> - Original Message - > On Wed, Jan 13, 2016 at

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Great post Ben, I largely agree with what you are saying, a lot of your points are valid concerns that I share. Just a couple of comments inline as I try to avoid what others have said. On 22 January 2016 at 17:24, Ben Nemec wrote: > So I haven't weighed in on this yet,

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 26 January 2016 at 16:01, Ben Nemec wrote: > On 01/26/2016 03:46 AM, Steven Hardy wrote: > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > >> On 01/25/2016 03:56 PM, Steven Hardy wrote: > >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 27 January 2016 at 08:10, Tzu-Mainn Chen wrote: > > Okay, so I initially thought we weren't making much progress on this > > discussion, but after some more thought and reading of the existing PoC, > > we're (maybe?) less far apart than I initially thought. > > > > I

Re: [openstack-dev] [tripleo] Logo for TripleO

On 11 March 2016 at 05:32, Jason Rist wrote: > Hey everyone - > We've been working on a UI for TripleO for a few months now and > we're > just about to beg to be a part of upstream... and we're in need of a > logo for the login page and header. > > In my evenings, I've

Re: [openstack-dev] [TripleO] core cleanup

On 14 March 2016 at 14:26, Dan Prince wrote: > Looking at the stats for the last 180 days I'd like to propose we > cleanup TripleO core a bit: > > http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt > > There are a few reviewers with low numbers of reviews

Re: [openstack-dev] [TripleO] propose ejuaso for core

On 14 March 2016 at 14:38, Dan Prince wrote: > http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt > > Our top reviewer over the last half a year ejuaso (goes by Ozz for > Osorio or jaosorior on IRC). His reviews seem consistent, he > consistently attends the

Re: [openstack-dev] [TripleO] propose EmilienM for core

On 20 March 2016 at 18:22, Dan Prince wrote: > I'd like to propose that we add Emilien Macchi to the TripleO core > review team. Emilien has been getting more involved with TripleO during > this last release. In addition to help with various Puppet things he > also has

Re: [openstack-dev] [TripleO] propose trown for core

On 20 March 2016 at 18:32, Dan Prince wrote: > I'd like to propose that we add John Trowbridge to the TripleO core > review team. John has become one of the goto guys in helping to chase > down upstream trunk chasing issues. He has contributed a lot to helping > keep general

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On 29 February 2016 at 17:32, Ana Krivokapic wrote: > On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince wrote: > > There is a new projects for the ui called tripleo-ui. As most of the > > existing TripleO core members aren't going to be reviewing UI specific >

Re: [openstack-dev] [tripleo] Zaqar messages standardization

On 20 May 2016 at 18:39, Dan Prince wrote: > On Fri, 2016-05-20 at 17:52 +0200, Jiri Tomasek wrote: > > Hey all, > > > > I've been recently working on getting the TripleO UI integrated with > > Zaqar, so it can receive a messages from Mistral workflows and act > > upon them

Re: [openstack-dev] [TripleO] [UI] Version

On Wednesday, 27 July 2016, Steven Hardy <sha...@redhat.com> wrote: > On Wed, Jul 27, 2016 at 02:08:08PM +0100, Dougal Matthews wrote: > >On 27 July 2016 at 12:41, Honza Pokorny <ho...@redhat.com > <javascript:;>> wrote: > > > > Hello fol

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On 19 July 2016 at 16:20, Steven Hardy wrote: > On Mon, Jul 18, 2016 at 12:28:10PM +0100, Julie Pichon wrote: > > Hi, > > > > On Friday Dougal mentioned on IRC that he hadn't realised there was a > > separate project for tripleo-common bugs on Launchpad [1] and that he'd > >

Re: [openstack-dev] [TripleO] [UI] Version

On 27 July 2016 at 12:41, Honza Pokorny wrote: > Hello folks, > > As the tripleo-ui project is quickly maturing, it might be time to start > versioning our code. As of now, the version is set to 0.0.1 and that > hardly reflects the state of the project. > > What do you think?

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 28 June 2016 at 06:38, Jason Rist <jr...@redhat.com> wrote: > On 06/27/2016 06:57 AM, Dougal Matthews wrote: > > On 27 June 2016 at 07:45, Renat Akhmerov <renat.akhme...@gmail.com> > wrote: > > > > > > > >> Ideally it would

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

On 27 June 2016 at 14:30, Alexey Khivin wrote: > Hello, Moshe > > Tomorrow I discovered yaqluator.com for myself! Thanks for the useful > tool! > > But suddenly I was said that the expression > [1,2].join([3], true, [$1, $2]) > evaluated to [[1,3]] on the yaqluator > > A the

Re: [openstack-dev] [mistral] Cancelling team meeting today - 06/27/2016

Last week the topic of timeslot came up, would it be good to start that discussion? Maybe we can have a vote on slots, and since we would need the PTL to attend it would be best to start with a list of times that work for you. Or, if most people are happy with the current time, we can just stick

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 27 June 2016 at 07:45, Renat Akhmerov wrote: > > > Ideally it would be nice to have something that matches the meaning of > the > > name. Maybe we can combine wind with one of the other ideas. > > > > I like the idea of the logo being a stylized wind turbine. Perhaps

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

ce3-20d0-47b2-84f2-7bd1cb2bf9f7 >> { >> "output_expr": [ >> [ >> 1, >> 3 >> ] >> ] >> } >> >> >> As Matthews pointed out, the yaqluator is indeed OpenSource and >> con

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

+1 On 31 January 2017 at 16:02, Ben Nemec wrote: > In the spirit of all the core team changes, here are a couple more I'd > like to propose. > > Dmitry has been very helpful reviewing in instack-undercloud for a long > time so this is way overdue. I'm also going to

Re: [openstack-dev] [tripleo] Deployment plan management efforts sync up

On 2 February 2017 at 11:56, Jiri Tomasek wrote: > Hello all, > > there has been several ongoing efforts in TripleO regarding Deployment > Plans management and Deployment configuration itself. A lot of this work is > done to satisfy certain individual requirements but I

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On 24 January 2017 at 16:16, Mikhail Fedosin wrote: > Hey, Flavio :) Thanks for your questions! > > As you said currently only Nokia's adopting Glare for its own platform, > but if we talk about OpenStack, that I believe Mistral will start to use it > soon. > Has there been

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

+1! On 23 January 2017 at 19:03, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on

Re: [openstack-dev] [tripleo] Proposing Honza Pokorny core on tripleo-ui

+1! On 25 January 2017 at 15:28, Steven Hardy wrote: > On Tue, Jan 24, 2017 at 08:52:51AM -0500, Emilien Macchi wrote: > > I have been discussed with TripleO UI core reviewers and it's pretty > > clear Honza's work has been valuable so we can propose him part of > > Tripleo

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

+1! On 26 January 2017 at 18:36, Harry Rybacki wrote: > On Thu, Jan 26, 2017 at 12:25 PM, Martin André wrote: > > On Tue, Jan 24, 2017 at 6:03 PM, Juan Antonio Osorio > > wrote: > >> Sagi (sshnaidm on IRC) has done significant work

Re: [openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

larger ecosystem of actions that can be installed, they don't all need to be included with Mistral itself. > Thoughts? > > Renat Akhmerov > @Nokia > > On 12 Jan 2017, at 22:27, Dougal Matthews <dou...@redhat.com> wrote: > > Hey all, > > I just wanted to share a

Re: [openstack-dev] [TripleO][CI]

On 15 January 2017 at 20:24, Sagi Shnaidman wrote: > Hi, all > > FYI, the periodic TripleO nonha jobs fail because of introspection > failure, there is opened bug in mistral: > > Ironic introspection fails because unexpected keyword "insecure" >

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

On 1 March 2017 at 16:47, Renat Akhmerov wrote: > Hi, > > Based on the stats of Michal Gershenzon in Ocata cycle I’d like to promote > her to the core team. > Michal works at Nokia CloudBand and being a CloudBand engineer she knows > Mistral very well > as a user and

Re: [openstack-dev] [TripleO][Containers] Creating launchpad bugs and correct tags

On 2 March 2017 at 10:40, Flavio Percoco wrote: > Greetings, > > Just wanted to give a heads up that we're tagging all the containers > related > bugs with the... guess what?... containers tag. If you find an issue with > one of > the containers jobs or running tripleo on

[openstack-dev] [TripleO] Mistral transition status for RC1

Hey, This is just a quick update on the Mistral API transition. We are now at a point where all the major CLI commands (node registration, introspection and deployment) are being powered by mistral workflows. We have an etherpad that is tracking all the reviews in quite a bit of detail:

Re: [openstack-dev] [tripleo] CI is currently down: 2 blockers

For those interested we now have a minimal way to reproduce the MessagingTimeout in Mistral. https://bugs.launchpad.net/mistral/+bug/1624284 It seems to be related to this change in Mistral: https://github.com/openstack/mistral/commit/1b0f0cddd620a3785017bb28d432cb0030b627d7 And even more

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

On 15 September 2016 at 10:20, Steven Hardy wrote: > Hi all, > > As we work to finish the last remaining tasks for Newton, it's a good time > to look back over the cycle, and recognize the excellent work done by > several new contributors. > > We've seen a different

  1   2   >