Re: [openstack-dev] [Fuel][Infra] Nailgun extensions testing

Hi Roman, >> reasonable to just install it from PyPi (first we need to release Nailgun to PyPi) Yes there will be dependencies, but there should be a way to test core extensions (those which go to standard Fuel build) from master (or any other branch), so installing from pypi is not always an

[openstack-dev] [Fuel] [shotgun] New shotgun2 command: short-report

Hi, all Just wanted to inform you, that shotgun2 now has new command short-report, which allows you to receive shorter and cleaner output for attaching to bug description, sharing, etc. Usage: shotgun2 short-report Example output: http://paste.openstack.org/show/491256/ Regards, Volodymyr

Re: [openstack-dev] [Fuel][Infra] Nailgun extensions testing

The idea is to write python (or shell) script which will: > - clone all required repos (like fuel-web, extensions repos) using > probably zuul-cloner Doesn’t nodepool automatically do that? > - checkout to appropriate stable branches / will cherry-pick some > commit / stay on master As far

[openstack-dev] [Fuel][plugins] stable/mitaka branches for plugins

Hey fuelers, We’re getting ready for Mitaka SCF in all things Fuel and plugins are currently a somewhat grey area. So I’d like to discuss which plugins should have stable/mitaka branches. We’re currently testing 3 plugins as a part of Swarm testing suite, so at least these 3 look like hard

[openstack-dev] [Fuel][Bareon][Ironic] The future of integration module

Hi, I would like to bring up discussion on Bareon [0] and Ironic integration and plans for the future. But first let me provide background information on the topic. Bareon is partitioning/provisioning system [1] which is based on Fuel-agent [2], currently it's in active development and will be

Re: [openstack-dev] [Fuel][Nailgun] Random failures in unit tests

FakeUI, which is based on fake threads, is obviously needed for development purposes. Ideally we need to refactor our integration tests, so that we don't run whole pipeline in every test. To start, I suggest that we switch from threads to synchronous runs of test cases (while keeping threads for

[openstack-dev] [Fuel] Packaging CI for Fuel

Hi, everyone, we'd like to announce Packaging CI for Fuel. For now there are no extended tests, just package builds. Package-based test will be added later in Newton development cycle. Current workflow: * for every request we build a package and publish it to temporary repository, which you

Re: [openstack-dev] [Fuel] [FFE] LCM readiness for all deployment tasks

Hi, Feature has been merged. QA is in progress. Thanks, Szymon On 4 March, 2016 at 1:31:55, Dmitry Borodaenko (dborodae...@mirantis.com) wrote: Granted, merge deadline March 15. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 05:03:11PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to

[openstack-dev] [Fuel][Nailgun] Random failures in unit tests

Hey Fuelers, As you might know recently we encounter a lot of random test failures on CI, and they are still there (likely with a bit less probability). A nature of that random failures is actually not a random, they are happened because of so called fake threads. Fake threads, actually, ain't

Re: [openstack-dev] [Fuel][FFE] FF exception request for HugePages

Folks, Majority of the commits for HugePages feature are merged in time [0]. One commit for validation is still to be merged [1]. So we would ask for 2 more days to complete the feature. Regards, Dmitry. [0] https://review.openstack.org/#/q/status:merged+AND+topic:bp/support-hugepages [1]

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

Hi Evgeniy, On Fri, Mar 18, 2016 at 4:26 PM, Evgeniy L wrote: > > >> On the other side, there is ongoing work to have an ansible-based deploy >> ramdisk in Ironic, maybe inspector could benefit from it too. Didn't think >> about it yet, would be interesting to discuss on the

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

Sorry, typo: *cloud case does NOT assume running any kind of agent inside user instance Vladimir Kozhukalov On Fri, Mar 18, 2016 at 7:26 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > >Well, there's a number of reasons. Ironic is not meant only for an > >"undercloud" (deploying

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

>Well, there's a number of reasons. Ironic is not meant only for an >"undercloud" (deploying OpenStack on ironic instances). There are both >public and private cloud deployments of ironic in production today, that >make bare metal instances available to users of the cloud. Those users >may not

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

Hi, > Are there any effort on OpenStack packaging? The short answer is yes. We are putting efforts to migrate all our packaging activities to the community RPM/DEB projects. Long story is as follows: At the moment Fuel is distributed as a set of RPM packages. This Packaging CI that Aleksandra

[openstack-dev] [Fuel][Infra] Nailgun extensions testing

Hi everyone! I’m looking for boilerplates/good practices regarding to testing extensions with core code. Since we unlocked Nailgun extensions system [0] and now there is a possibility to install the extensions from external sources we want to also provide a way to test your own extensions

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

On 2016-03-19 05:10:18 -0500 (-0500), Monty Taylor wrote: [...] > It would also be good to tie off with the security team about > this. One of the reasons we stopped publishing debs years ago is > that it made us a de-facto derivative distro. People were using > our packages in production,

Re: [openstack-dev] [Fuel][FFE] FF exception request for HugePages

FFE extension granted until March 18 for: https://review.openstack.org/#/c/286495/ On Wed, Mar 16, 2016 at 10:46:41PM +0300, Dmitry Klenov wrote: > Folks, > > Majority of the commits for HugePages feature are merged in time [0]. > > One commit for validation is still to be merged [1]. So we

Re: [openstack-dev] [Fuel][Nailgun] Random failures in unit tests

Hey Vitaly, Thanks for your feedback, it's an important notice. However, I think you didn't get the problem quite well so let me explain it again. You see, Nailgun unit tests are failing due to races or deadlocks happened by two transactions: test transaction and fake thread transaction, and we

Re: [openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

Folks, Majority of the commits for Numa and CPU pinning feature are merged in time [0]. One commit for validation is still to be merged [1]. So we would need 2 more days to complete the feature. Regards, Dmitry. [0]

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On 03/16/2016 01:39 PM, Evgeniy L wrote: Hi Dmitry, I can try to provide you description on what current Nailgun agent is, and what are potential requirements we may need from HW discovery system. Nailgun agent is a one-file Ruby script [0] which is periodically run under cron. It collects

Re: [openstack-dev] [Fuel] Plans on networking modularisation

Hi Ryan, Thank you. We had a talk with Evgeniy. As a preliminary plan, we will have meetings with all interested people from Networking team. Regards, Aleksey Kasatkin On Tue, Mar 15, 2016 at 7:46 PM, Ryan Moe wrote: > Hi Aleksey, > > > >> What is the status of making

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

Are they any effort on OpenStack packaging? http://governance.openstack.org/reference/projects/packaging-deb.html http://governance.openstack.org/reference/projects/packaging-rpm.html I would like to see packaging built & tested by OpenStack Infra, so downstream CI (Fuel, Puppet OpenStack,

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

On 03/16/2016 06:22 PM, Emilien Macchi wrote: > Are they any effort on OpenStack packaging? > > http://governance.openstack.org/reference/projects/packaging-deb.html > http://governance.openstack.org/reference/projects/packaging-rpm.html > > I would like to see packaging built & tested by

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On Fri, Mar 18, 2016 at 07:26:03PM +0300, Vladimir Kozhukalov wrote: > >Well, there's a number of reasons. Ironic is not meant only for an > >"undercloud" (deploying OpenStack on ironic instances). There are both > >public and private cloud deployments of ironic in production today, that > >make

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On Fri, Mar 18, 2016 at 05:26:13PM +0300, Evgeniy L wrote: > On Thu, Mar 17, 2016 at 3:16 PM, Dmitry Tantsur wrote: > > > On 03/16/2016 01:39 PM, Evgeniy L wrote: > > > >> Hi Dmitry, > >> > >> I can try to provide you description on what current Nailgun agent is, > >> and

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

On 03/17/2016 03:11 PM, Thomas Goirand wrote: On 03/16/2016 06:22 PM, Emilien Macchi wrote: Are they any effort on OpenStack packaging? http://governance.openstack.org/reference/projects/packaging-deb.html http://governance.openstack.org/reference/projects/packaging-rpm.html I would like to

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On Thu, Mar 17, 2016 at 3:16 PM, Dmitry Tantsur wrote: > On 03/16/2016 01:39 PM, Evgeniy L wrote: > >> Hi Dmitry, >> >> I can try to provide you description on what current Nailgun agent is, >> and what are potential requirements we may need from HW discovery system. >> >>

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

Hi Dmitry, I can try to provide you description on what current Nailgun agent is, and what are potential requirements we may need from HW discovery system. Nailgun agent is a one-file Ruby script [0] which is periodically run under cron. It collects information about HW using ohai [1], plus it

Re: [openstack-dev] [Fuel] Getting rid of cluster status

On 03/16/2016 11:53 AM, Vladimir Kuklin wrote: > Folks > > As I generally support the idea of getting rid of cluster status, this > requires thorough design. My opinion here is that we should leave it as > a function of nodes state until we come up with a variant of better > calculation of

Re: [openstack-dev] [Fuel][Nailgun] Random failures in unit tests

Igor, We have UI and CLI integration tests which use fake mode of Nailgun, and we can't avoid using fake threads for them. So I think we need to think how to fix fake threads instead. There is a critical bug which is the main reason of randomly

Re: [openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

FFE extension granted until March 18 for: https://review.openstack.org/#/c/285282/ On Wed, Mar 16, 2016 at 10:48:31PM +0300, Dmitry Klenov wrote: > Folks, > > Majority of the commits for Numa and CPU pinning feature are merged in time > [0]. > > One commit for validation is still to be merged

Re: [openstack-dev] [Fuel] fuel-web/docs to fuel-docs migration

Hi, everyone, we've merged migration changes. Please send all new documentation patches to openstack/fuel-docs repository. Development documentation is available there in devdocs/ subfolder. On Tue, Mar 15, 2016 at 2:41 PM, Aleksandra Fedorova wrote: > Hi, everyone, > >

Re: [openstack-dev] [Fuel] Getting rid of cluster status

Folks As I generally support the idea of getting rid of cluster status, this requires thorough design. My opinion here is that we should leave it as a function of nodes state until we come up with a variant of better calculation of cluster status. Nevertheless it is true that cluster status is

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

On 03/15/2016 01:53 PM, Serge Kovaleff wrote: Dear All, Let's compare functional abilities of both solutions. Till the recent Mitaka release Ironic-inspector had only Introspection ability. Discovery part is proposed and implemented by Anton Arefiev. We should align expectations and current

Re: [openstack-dev] [Fuel] Getting rid of cluster status

On Tue, Mar 15, 2016 at 4:04 AM Roman Prykhodchenko wrote: > Fuelers, > > I would like to continue the series of "Getting rid of …" emails. This > time I’d like to talk about statuses of clusters. > > The issues with that attribute is that it is not actually related to real >

[openstack-dev] [fuel] UCA deployment landed and working

Hi all, Thanks to Alex Schultz, we landed the Ubuntu Cloud Archive as a possible deployment source last week just in time for the feature freeze exception. No sooner than landing it, we have a new task to switch it to a separate Fuel release[1]. Patches are on review to fix this now[2]. But now

Re: [openstack-dev] [Fuel] Plans on networking modularisation

Hi Aleksey, > What is the status of making networking part replaceable? As I know, [0] > is in progress. Are there any other activities in progress (about API, > serialization for orchestrator, network verification)? Do we have specs on > review (I know about this one: [1]) ? > > AFAIK there

Re: [openstack-dev] [Fuel] [FFE] FF exception request for SR-IOV

Hi, feature has been merged. QA is in progress. Thanks, Alex On Fri, Mar 4, 2016 at 1:15 AM, Dmitry Borodaenko wrote: > Granted, merge deadline March 16, feature to be marked experimental > until QA has signed off that it's fully tested and stable. > > -- > Dmitry

Re: [openstack-dev] [Fuel] network_metadata hash keys on astute.yaml

Keys should be immutable. If keys are not immutable -- it can lead to the situation, when network_metadata/nodes contains two records for same nodes (with same UID), but with different information. /sv __ OpenStack

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

+1 to drop nailgun-agent and replace it with python script with ohai call or ironic-inspector! On Tue, Mar 15, 2016 at 1:07 PM, Alexander Saprykin wrote: > Dear all, > > Thank you for the opinions about this problem. > > I would agree with Roman, that it is always better

Re: [openstack-dev] [Fuel] network_metadata hash keys on astute.yaml

Hi, I'm agree with Alex, keys should remain immutable. 'node-{uid}' is Okay, we have a method for this in Nailgun already. It should be a very simple fix in Nailgun. Thanks, Aleksey Kasatkin On Tue, Mar 15, 2016 at 3:19 PM, Kyrylo Galanov wrote: > Hi, > > I would

Re: [openstack-dev] [Fuel] network_metadata hash keys on astute.yaml

Hi, I would like to remind that we are close to code freeze and bug is still there. Moreover, new bug reports continue to be submitted [3]. Please, do not ignore the discussion. [3] https://bugs.launchpad.net/fuel/+bug/1557417 On Tue, Mar 15, 2016 at 10:18 PM, Aleksandr Didenko

Re: [openstack-dev] [Fuel] [ironic] [inspector] Rewriting nailgun agent on Python proposal

Dear All, Let's compare functional abilities of both solutions. Till the recent Mitaka release Ironic-inspector had only Introspection ability. Discovery part is proposed and implemented by Anton Arefiev. We should align expectations and current and future functionality. Adding Tags to attract

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Dear all, Thank you for the opinions about this problem. I would agree with Roman, that it is always better to reuse solutions than re-inventing the wheel. We should investigate possibility of using ironic-inspector and integrating it into fuel. Best regards, Alexander Saprykin 2016-03-15

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

My strong +1 to drop off nailgun-agent completely in favour of ironic-inspector. Even taking into consideration we'lll need to extend ironic-inspector for fuel needs. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Tue, Mar 15, 2016 at 11:06 AM, Roman Prykhodchenko

[openstack-dev] [Fuel] fuel-web/docs to fuel-docs migration

Hi, everyone, this week we plan to migrate the content of fuel-web/docs to fuel-docs repo to setup one place for all Fuel documentation. See related blueprint https://blueprints.launchpad.net/fuel/+spec/fuel-docs-migration There are two patches on review: *

Re: [openstack-dev] [Fuel] network_metadata hash keys on astute.yaml

Hi, some additional info on the problem: if I create some Hiera override for the nodes list and use node key which is hostname bond, then after node rename (rename during LCM or reset/rename/redeploy - doesn't matter) my override will create a "ghost" node in the list and will not change settings

[openstack-dev] [Fuel] Getting rid of cluster status

Fuelers, I would like to continue the series of "Getting rid of …" emails. This time I’d like to talk about statuses of clusters. The issues with that attribute is that it is not actually related to real world very much and represents nothing. A few month ago I proposed to make it more

Re: [openstack-dev] [Fuel] Plans on networking modularisation

Hi, Evgeniy, thank you for summarizing this. I have questions about action items. What is the status of making networking part replaceable? As I know, [0] is in progress. Are there any other activities in progress (about API, serialization for orchestrator, network verification)? Do we have

[openstack-dev] [Fuel] network_metadata hash keys on astute.yaml

Hi, Currently nailgun and puppet process network_metadata hash slightly different. Nailgun uses short hostname as a hash key for each node, while library code assumes that key is always 'node-{uid}'. Sometimes it can result in a deployment failure. During code review[0] it turned out that there

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

My opition on this is that we have too many re-invented wheels in Fuel and it’s better think about replacing them with something we can re-use than re-inventing them one more time. Let’s take a look at Ironic and try to figure out how we can use its features for the same purpose. - romcheg >

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

On 15/03/16 07:11, Vladimir Kozhukalov wrote: > Alexander, > > We have many other places where use Ruby (astute, puppet custom types, > etc.). I don't think it is a good reason to re-write something just > because it is written in Ruby. You are right about tests, about plugins, > but let's look

[openstack-dev] [Fuel] Plans on networking modularisation

Hi, We've been working on networking modularisation, during this activity Nailgun is being fixed [0] in order to provide better layer boundary between network related code and the rest of the system. The purpose of this email is: 1. To make sure that this activity is known in Fuel team. 2. To

[openstack-dev] [Fuel] PTL Candidacy

Hi all, I'd like to announce my candidacy to be Fuel PTL for the Newton cycle. I've been a member of Fuel team since the very beginning of the project. Fuel started as a proprietary deployment tool for OpenStack, but since that we have been smothly moving towards being more and more open and more

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Alexander, We have many other places where use Ruby (astute, puppet custom types, etc.). I don't think it is a good reason to re-write something just because it is written in Ruby. You are right about tests, about plugins, but let's look around. Ironic community has already invented discovery

Re: [openstack-dev] [fuel] PTL Non-Candidacy

Dmitry, thanks for your work over the last months. I would like to personally thank you because you highly contributed to the collaboration with Puppet OpenStack group, and after almost a year, we can see that as a success story. Fuel has some background because it was not part of big tent;

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Hi Alexander, thanks for bringing this up. >From your list of problems the only problem which I see is 1st, 2nd and 3rd are solvable even with current implementation. Also I don't think that we should continue developing our own HW discovery mechanism, we should consider switching to

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

On 03/14/2016 04:13 PM, Alexander Saprykin wrote: > Hi, > > We have fuel-nailgun-agent project which was initially written on Ruby. > It is 900 lines of code single script, that collects and provides to the > nailgun information about node's hardware. > > In the past several iteration we had to

[openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Hi, We have fuel-nailgun-agent project which was initially written on Ruby. It is 900 lines of code single script, that collects and provides to the nailgun information about node's hardware. In the past several iteration we had to introduce new modifications to that script we discovered couple

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Folks, I’ve registered a blueprint [1] and created an etherpad document [2] where we can co-work on the spec before posting it to a formal review. Let’s cooperate to summarize what we need to do. 1. https://blueprints.launchpad.net/fuel/+spec/remove-logs-from-nailgun 2.

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

+1 to Vitaliy, it would be nice find somewhere a details for migration. And one more concern I should highlight - for some users logless UI may be challenging thing. The logs removing shouldn't affect the UX. Nastya. On Sat, Mar 12, 2016 at 3:08 AM, Andrew Woodward wrote: >

[openstack-dev] [fuel] PTL Non-Candidacy

All, I will not be running for Fuel PTL for the Newton cycle. There are many reasons why I think it's a good idea for me to step down: Fuel is a large project. In Mitaka, 224 contributors made 3200+ commits changing 700K+ lines of code [0]. That's on par with the most active OpenStack projects

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Thanks for working this out! Confirming that task history remains included in the scope of this FFE until the merge deadline, March 24. On Fri, Mar 11, 2016 at 11:48:51PM +0200, Igor Kalnitsky wrote: > Hey Dmitry, > > I confirm that we agreed on feature design, and you can proceed with >

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

I think we can address it by retaining deployment logs in nailgun/ui, this also removes the chicken and egg problem. after LMA is deployed it can be allowed to re-own 'logs' button on UI once it's deployed, including redirecting fuel logs there. On Fri, Mar 11, 2016 at 2:07 PM Mike Scherbakov

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

Matthew, congrats! On Fri, Mar 11, 2016 at 10:59 PM, Sergii Golovatiuk < sgolovat...@mirantis.com> wrote: > Hi, > > Personally, I give my +2 to Matthew without any doubts. Matthew reviews > has a lot of technical details and guidances. As always he is bright > helping people over IRC or mailing

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

We can sort out details later. In a worst case, the warning will be there in Newton too, and feature will go away only in O* release. So let's proceed with the bug.. On Fri, Mar 11, 2016 at 1:02 PM Vitaly Kramskikh wrote: > We can add the warning, but I think before we

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Hey Dmitry, I confirm that we agreed on feature design, and you can proceed with granting exception. ,- Igor On Fri, Mar 11, 2016 at 8:27 PM, Alexey Shtokolov wrote: > Hi Dmitry, > > We've reached the design consensus with Igor today. Could you please remove > the

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

We can add the warning, but I think before we do this we should have clear migration plan. According to this thread, some parts are still not clear. 2016-03-11 22:00 GMT+03:00 Mike Scherbakov : > Deprecation warning for Fuel Mitaka: >

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Deprecation warning for Fuel Mitaka: https://bugs.launchpad.net/fuel/+bug/1556244. On Fri, Mar 11, 2016 at 8:59 AM Roman Prykhodchenko wrote: > Since there are a lot of supporters for this idea, what do you folks think > about creating a BP spec where we can describe what we

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Hi Dmitry, We've reached the design consensus with Igor today. Could you please remove the conditional status of the FFE request? As agreed: the merge deadline is March 24. -- WBR, Alexey Shtokolov 2016-03-11 2:27 GMT+03:00 Dmitry Borodaenko : > Granted. Design

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Since there are a lot of supporters for this idea, what do you folks think about creating a BP spec where we can describe what we should do in order to remove logs from UI and Nailgun? I also propose to file a bug about adding a deprecation warning to Mitaka release of Fuel. > 11 бер. 2016 р.

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

On 03/11/2016 04:46 PM, Mike Scherbakov wrote: > +1 to remove logs from Fuel UI in Fuel Newton. > In Fuel Mitaka we'd need to put a deprecation warning somewhere. I agree, there is not much sense having non flexible (no content filters) logs view in UI. LMA plugins shall cover this area as well.

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

+1 to remove logs from Fuel UI in Fuel Newton. In Fuel Mitaka we'd need to put a deprecation warning somewhere. On Fri, Mar 11, 2016, 04:57 Patrick Petit wrote: > > On 11 March 2016 at 12:51:40, Igor Kalnitsky (ikalnit...@mirantis.com) > wrote: > > Patrick, > > Sorry, but I

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

On 11 March 2016 at 15:45:57, Simon Pasquier (spasqu...@mirantis.com) wrote: Thanks for kicking off the discussion! On Thu, Mar 10, 2016 at 8:30 AM, Mike Scherbakov wrote: Hi folks, in order to make a decision whether we need to support example plugins, and if

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Thanks for kicking off the discussion! On Thu, Mar 10, 2016 at 8:30 AM, Mike Scherbakov wrote: > Hi folks, > in order to make a decision whether we need to support example plugins, > and if actually need them [1], I'd suggest to discuss more common things > about

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

On 11 March 2016 at 12:51:40, Igor Kalnitsky (ikalnit...@mirantis.com) wrote: Patrick,  Sorry, but I meant another question. I thought that LMA plugin should  be installed in some environment before we can start use it. Is this a  case? If so, it means we can't use for master node until some 

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Patrick, Sorry, but I meant another question. I thought that LMA plugin should be installed in some environment before we can start use it. Is this a case? If so, it means we can't use for master node until some environment is deployed. On Fri, Mar 11, 2016 at 12:52 PM, Patrick Petit

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

On 11 March 2016 at 11:34:32, Igor Kalnitsky (ikalnit...@mirantis.com) wrote: Hey Roman, Thank you for bringing this up. +1 from my side, especially taking into account the patch where we tried to solve logrotated logs problem [1]. It's complex and unsupportable, as well as already existed

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Hey Roman, Thank you for bringing this up. +1 from my side, especially taking into account the patch where we tried to solve logrotated logs problem [1]. It's complex and unsupportable, as well as already existed logview code in Nailgun. Patrick, Simon, Does LMA plugin support logs from master

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Fuelers, As Simon said, we already have a log centralisation solution for MOS delivered as a Fuel plugins known as StackLight / LMA toolset. And so objectively, there is no need to have log management in Nailgun anymore. To go one step further we suggested several times to have a StackLight

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Hi Mike, thanks for clarification. On Fri, Mar 11, 2016 at 9:42 AM, Mike Scherbakov wrote: > Thank you for comments folks. > Clarifications, with the feedback incorporated: > 1) We can install plugin developed against 8 to Fuel Mitaka (9). But it > won't appear in the

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Hi, +1, it's very hard to use current representation of logs for debugging, everybody goes to the node and tries to find required logs, instead of reimplementing debugging friendly tool it would be better to get something ready to use on the master. Thanks, On Fri, Mar 11, 2016 at 12:05 PM,

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Hello Roman, On Fri, Mar 11, 2016 at 9:57 AM, Roman Prykhodchenko wrote: > Fuelers, > > I remember we’ve discussing this topic in our couloirs before but I’d like > to bring that discussion to a more official format. > > Let me state a few reasons to do this: > > - Log

[openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

Fuelers, I remember we’ve discussing this topic in our couloirs before but I’d like to bring that discussion to a more official format. Let me state a few reasons to do this: - Log management code in Nailgun is overcomplicated - Working with logs on big scale deployments is barely possible

Re: [openstack-dev] [Fuel] Trouble mapping the Remote PXE node

Hi, Akshik Thanks for the email. Do you have nailgun logs with you? I guess, it would much more easier to debug this while having more diagnostic info. Please, file a bug at launchpad following the steps described here: https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Bugs then post the

[openstack-dev] [Fuel] Trouble mapping the Remote PXE node

Hi, I'm using Fuel 7.0, trying to evaluate remote compute and node group I've configured a remote PXE and I'm able to boot the node successfully onto the remote pxe, but while adding it to the environment and trying to configure interface I'm stuck with following error fuel node --node-id

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Thank you for comments folks. Clarifications, with the feedback incorporated: 1) We can install plugin developed against 8 to Fuel Mitaka (9). But it won't appear in the UI as available plugin. This is what I want to fix, and have just a warning that this plugin may not work. 2) To clarify, I'm

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Regarding #2 > we already generate from templates required information for a plugin developer to start development and it is great. So, back to what I said: > However, we can have fpb generating template plugin, with commented code in there. If you uncomment, you a get a comprehensive example of a

Re: [openstack-dev] [Fuel] FFE request for osnailyfacter refactoring for Puppet Master compatibility

Granted, merge deadlines are still as defined below: March 16 and 24. For the record, the spec for this feature: https://review.openstack.org/284853 The spec has positive votes from fuel-library CL and cores, so consensus is indeed reached. Get a +1 from the fuel-python CL and I'll merge it. --

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Granted. Design consensus deadline for the task history part of this feature is extended to March 11. This does not change the merge deadline for other parts of this feature, which is still March 24. -- Dmitry Borodaenko On Fri, Mar 11, 2016 at 01:02:52AM +0300, Alexey Shtokolov wrote: >

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Dmitry, We are really close to have the consensus, but we need one more meeting with Fuel-Python Component Lead Igor Kalnitsky to make the final decision. All patches [0] are on review. The meeting is scheduled for tomorrow (03/11 1:30pm CET). Could you please grant us one more day for it? [0] -

Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem: Inside VM "fuel-master"

Machara <samer.mach...@telecom-sudparis.eu> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [Fuel] [Openstack] Instalation Problem: > Inside VM "fuel-master&quo

Re: [openstack-dev] [Fuel] FFE request for osnailyfacter refactoring for Puppet Master compatibility

Hi Dmitry, We have reached design agreement on this feature as of this morning, March 10th. The spec has been accepted and the test/merge plan presented for remaining patches by March 24 was agreed upon. Can the conditional status of the FFE request be removed, please? Thanks, Scott

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Well, what about tomorrow? On SCF we create stable branches and master is open for next release. You probably will want to run those tests against Fuel 10, and FPB's master won't have that "10" release in examples metadata. Because it's something that we usually don't want to release, and FPB

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

> Good idea. That should be done despite on any decision we will take. Currently you have to specify which releases your plugin supports [0]. So I can take my plugin developed for 8.0 and install it on Fuel-9.0 (I actually did it and it worked just fine). But I won't be able to enable this plugin

Re: [openstack-dev] [fuel][Fuel-web] : make html command not working

Hey Prameswar, That't because dependencies weren't installed. I can't remember which ones are required for building docs so my suggestion is to install them all. $ virtualenv venv $ . venv/bin/activate $ pip install -r ../nailgun/test-requirements.txt $ make html Let me know if

Re: [openstack-dev] [Fuel] UI code freeze

​Evge​niy, Right. There is only nailgun python project, development documentation [1] and some minor scripts [2] which are outdated. Our further plan is to move nailgun itself to a separate repo fuel-nailgun, remove outdated code, and then move development doc pages to corresponding git repos.

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

Hi All, I'm very appreciate being a part of the Fuel project as core reviewers team! Thank you all for nomination and for +1s! On Thu, Mar 10, 2016 at 12:40 PM, Sergey Kulanov wrote: > Voting period is over and there's no objections from cores. > So Maksim, welcome to

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

Voting period is over and there's no objections from cores. So Maksim, welcome to fuel-virtualbox-core group. Congrats! 2016-03-09 13:33 GMT+02:00 Sergii Golovatiuk : > +1 > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Wed, Mar 9,

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

On 10.03.2016 08:30, Mike Scherbakov wrote: > Hi folks, > in order to make a decision whether we need to support example plugins, > and if actually need them [1], I'd suggest to discuss more common things > about plugins. > > My thoughts: > 1) This is not good, that our plugins created for Fuel 8

<    1   2   3   4   5   6   7   8   9   10   >