Here is an etherpad with all of the open patches that Chandan and I have
been working on.
https://etherpad.openstack.org/p/selenium-testing-ci
On 2018-10-22 18:25, Chandan kumar wrote:
> Hello Honza,
>
> On Thu, Oct 18, 2018 at 6:15 PM Bogdan Dobrelya wrote:
> >
> > On 10
breakage before a patch is even merged.
Here are a few questions:
* Do you think this is a good idea?
* Could we accomplish this by some other, simple mechanism?
Any helpful suggestions, corrections, and feedback are much appreciated.
Thanks
Honza Pokorny
[1]: https://blueprints.launchpad.net
On 2018-08-31 13:17, Dougal Matthews wrote:
> On 31 August 2018 at 12:11, Steven Hardy wrote:
>
> > On Thu, Aug 30, 2018 at 3:28 PM, Honza Pokorny wrote:
> > > Hello!
> > >
> > > Over the last few months, it seems that tripleo-quickstart has evolved
>
Hello!
Over the last few months, it seems that tripleo-quickstart has evolved
into a CI tool. It's primarily used by computers, and not humans.
tripleo-quickstart is a helpful set of ansible playbooks, and a
collection of feature sets. However, it's become less useful for
setting up development
d gate job will fail because the dependency isn't in -deps RPM
4. We ask RDO to review for licensing
5. Once reviewed, new -deps package is built
6. Recheck
7. All jobs pass
There is the obvious issue with building an RPM based on an unmerged patch.
What do you think? Is that possible? Any oth
job succeeded. I
checked the tarballs listing, and the file is in fact present. Our
project doesn't produce any other release artifacts upstream.
Please direct any future failures to me (in addition to the mailing list
of course)
Thanks
Honza Pokorny
On 2017-11-21 21:34, Emilien Macchi wrote
.
If there are no objections within a week, we'll proceed with adding Ana
to the team.
Thanks
Honza Pokorny
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
On 2017-09-13 12:45, Dan Prince wrote:
> On Tue, Sep 12, 2017 at 9:58 PM, Jiri Tomasek wrote:
>
> > Hello all,
> >
> > As we are in the planning phase for Queens cycle, I'd like to open the
> > discussion on the topic of CLI (tripleoclient) and GUI (tripleo-ui) feature
> >
About 10 years ago, we were promised a fully semantic version of HTML.
No more nested divs to structure your documents. However, all we got
was a few generic, and only marginally useful elements like and
.
On 2017-08-03 18:59, Ana Krivokapic wrote:
> Hi TripleO devs,
>
> In our effort to make
; fact tripleo-ui testing wouldn't be possible without deploying the
> > tripleo-validations bits.
> >
> > > Florian
> > >
> > >
> > > > - Write a tempest plugin for tripleo-ui (like Horizon has one:
> > > > https://github.com/openstack/tempest
d be aware of?
Is there any documentation beyond what is in the git tree?
Any help would be appreciated
Thanks!
Honza Pokorny
[1]: https://github.com/openstack-infra/tripleo-ci
__
OpenStack Development Mailing List (not
+1
On 2017-04-06 11:53, Martin André wrote:
> Hellooo,
>
> I'd like to propose we extend Florian Fuchs +2 powers to the
> tripleo-validations project. Florian is already core on tripleo-ui
> (well, tripleo technically so this means there is no changes to make
> to gerrit groups).
>
> Florian
The included logs don't give me much to go on. It fails with a pretty
generic timeout message. I can't even determine if that happened during
"npm install" or after.
Is there any more information available on the source of the failure?
Thanks
Honza Pokorny
On 2017-02-16 12:43, Dou
Thanks everyone!
On 2017-01-30 10:45, Emilien Macchi wrote:
> Honza, you're now core on tripleo-ui project. Thanks for your hard
> work and congrats!
>
> On Fri, Jan 27, 2017 at 2:45 AM, Dougal Matthews wrote:
> > +1!
> >
> > On 25 January 2017 at 15:28, Steven Hardy
Thanks for being on top of this, Julie.
Honza Pokorny
On 2017-01-19 15:17, Julie Pichon wrote:
> On 18 January 2017 at 11:35, Julie Pichon <jpic...@redhat.com> wrote:
> > I'm sorry to report we're finding ourselves in the same situation
> > again - CI will fail on all t
Hello folks,
We've been using port 3000 for the GUI during development and testing.
Now that we're working on packaging and shipping our code, we're
wondering if port 3000 is still the best choice.
Would 3000 conflict with any other services? Is there a better option?
Thanks
Honza Pokorny
On 2016-07-27 14:18, Steven Hardy wrote:
> On Wed, Jul 27, 2016 at 08:41:32AM -0300, 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 t
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?
Honza Pokorny
Hello folks,
Here is a blueprint that describes a new feature for the tripleo GUI:
the network diagram.
https://blueprints.launchpad.net/tripleo-ui/+spec/network-diagram
I invite you to voice your opinions and share feedback.
Thanks
Honza Pokorny
the flavor instead of updating it in place is
because mistral and the nova client don't expose the "set_keys" API yet.
If the above patch receives favorable comments, we can work on getting
those APIs exposed in order to simplify the code in tripleo-common.
Hon
20 matches
Mail list logo