Re: [openstack-dev] [Fuel] Fuel - Rack Scale Architecture integration

[Andrian Noga]

Hi Deepti,

We have already a vision about Fuel-UI implementation for RSA.

I've replied already to you in private email.

Let's continue this thread in private conversation.

Regards,
Andrian Noga
Engineering Manager
Partner Integration Team,
Mirantis, Inc.
+38 (066) 811-84-12
Skype: bigfoot_ua
www.mirantis.com
an...@mirantis.com

On Fri, May 13, 2016 at 2:08 PM, <deepti.ramakris...@intel.com> wrote:

> Hello Fuel team,
>
> I am a software engineer working in the OpenStack team at Intel. You may
> have heard of Rack Scale Architecture [1] that Intel is pioneering. It is a
> new data center architecture that "simplifies resource management and
> provides the ability to dynamically compose resources based on
> workload-specific demands". It is supported by multiple industry partners.
>
> We would like to propose Fuel integration with this. The first step would
> be UI integration [2] and we would like to have a tab similar to the VMWare
> tab (whose visibility is controlled by a config flag) that talks to the
> Redfish API [3] for displaying resources such as pods, racks, etc as
> exposed by this API. Note that Redfish API is an open industry standard API
> supported by multiple companies.
>
> I plan to write up a blueprint/spec for the same, but I wanted to know if
> there is any immediate feedback on this idea before I even get started.
>
> Thanks,
> Deepti
>
> [1]
> http://www.intel.com/content/www/us/en/architecture-and-technology/intel-rack-scale-architecture.html
> [2] http://i.imgur.com/vLJIbwx.jpg
> [3] https://www.dmtf.org/standards/redfish
>
__
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] [Fuel] nova-network removal

[Andrian Noga]

Sheena,

I can confirm, that configurations with both DVS and NSX backends were
successfully tested for 7.0 by PI. This backend works also for 8.0

Regards,
Andrian

On Fri, Jan 15, 2016 at 10:03 PM, Sheena Gregson 
wrote:

> Adrian – can someone from the PI team please confirm what testing was
> performed?
>
>
>
> *From:* Roman Alekseenkov [mailto:ralekseen...@mirantis.com]
> *Sent:* Friday, January 15, 2016 11:30 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Fuel] nova-network removal
>
>
>
> I agree with Sheena. Sounds like removing support for nova-network would
> be the best option, even though it's late.
>
>
>
> However, I'd like us to think about the impact on vCenter integration.
> vCenter+nova-network was fully supported before. Since we are now
> recommending DVS or NSX backends, I'd like the team to explicitly confirm
> that those configurations have been tested.
>
>
>
> Thanks,
>
> Roman
>
>
>
> On Fri, Jan 15, 2016 at 6:43 AM, Sheena Gregson 
> wrote:
>
> Although we are very close to HCF, I see no option but to continue
> removing nova-network as I understand it is not currently functional or
> well-tested for the Mitaka release.  We must either remove it or test it,
> and we want to remove it anyway so that seems like the better path.
>
>
>
> *Mike*, what do you think?
>
>
>
> *From:* Roman Prykhodchenko [mailto:m...@romcheg.me]
> *Sent:* Friday, January 15, 2016 8:04 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Fuel] nova-network removal
>
>
>
> I’d like to add that nova-network support was removed from
> python-fuelclient in 8.0.
>
>
>
> 14 січ. 2016 р. о 17:54 Vitaly Kramskikh 
> написав(ла):
>
>
>
> Folks,
>
> We have a request on review which prohibits creating new envs with
> nova-network: https://review.openstack.org/#/c/261229/ We're 3 weeks away
> from HCF, and I think this is too late for such a change. What do you
> think? Should we proceed and remove nova-network support in 8.0, which is
> deprecated since 7.0?
>
>
> --
>
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
> __
> 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
>
>
>
>
> __
> 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
>
>
>
__
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

[openstack-dev] [Fuel][FFE] Provide possibilities to change VMware clusters on operational env

[Andrian Noga]

Colleagues,
I would like to request feature freeze exception for Provide possibilities
to change VMware clusters on operational env
https://blueprints.launchpad.net/fuel/+spec/add-vmware-clusters

Specification is ready for merge https://review.openstack.org/#/c/250469/12
Main patch for UI is already merged https://review.openstack.org/#/c/252358/
We still need to merge changes https://review.openstack.org/#/c/251278/
The change itself is a low risk patch.
 That should take just several days, so if there will be no other
objections, we will be able to merge the change in a week timeframe.


Regards,
Andrian Noga
Project manager
Partners Centric Engineering Team,
Mirantis, Inc.
+38 (063) 966-21-24
Skype: bigfoot_ua
www.mirantis.com
an...@mirantis.com
__
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

[openstack-dev] [Fuel][FFE] Component registry

[Andrian Noga]

Colleagues,

Folks,
I would like to request feature freeze exception for Component registry
https://blueprints.launchpad.net/fuel/+spec/component-registry

Specification is already merged https://review.openstack.org/#/c/229306/
Main patch is also merged https://review.openstack.org/#/c/247913/
We still need to merge UI changes https://review.openstack.org/#/c/246889/53
The change itself is a very small patch.
 That should take just several days, so if there will be no other
objections, we will be able to merge the change in a week timeframe.

Regards,
Andrian Noga
Project manager
Partners Centric Engineering Team,
Mirantis, Inc.
+38 (063) 966-21-24
Skype: bigfoot_ua
www.mirantis.com
an...@mirantis.com
__
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] [fuel] [FFE] FF Exception request for Deploy nova-compute (VCDriver) feature

[Andrian Noga]

Colleagues,
actually, i'm tottaly agree with Mike. We can merge
https://review.openstack.org/#/c/196114/ w/o additional Ceilometer support
(will be moved to next release). So if we merge it today we dont need FFE
for this feature.


Regards,
Andrian

On Fri, Jul 24, 2015 at 1:18 AM, Mike Scherbakov mscherba...@mirantis.com
wrote:

 Since we are in FF state already, I'd like to have urgent estimate from
 one of fuel-library cores:
 - holser
 - alex_didenko
 - aglarendil
 - bogdando

 aglarendil is on vacation though. Guys, please take a look at
 https://review.openstack.org/#/c/196114/ - can we accept it as exception?
 Seems to be good to go...

 I still think that additional Ceilometer support should be moved to the
 next release.

 Thanks,

 On Thu, Jul 23, 2015 at 1:56 PM Mike Scherbakov mscherba...@mirantis.com
 wrote:

 Hi Andrian,
 this is High priority blueprint [1] for 7.0 timeframe. It seems we still
 didn't merge the main part [2], and need FF exception for additional stuff.

 The question is about quality. If we focus on enhancements, then we don't
 focus on bugs. Which whether means to deliver work with lower quality of
 slip the release.

 My opinion is rather don't give FF exception in this case, and don't have
 Ceilometer support for this new feature.

 [1] https://blueprints.launchpad.net/fuel/+spec/compute-vmware-role
 [2] https://review.openstack.org/#/c/196114/

 On Thu, Jul 23, 2015 at 1:39 PM Andrian Noga an...@mirantis.com wrote:

 Hi,

 The patch patch for fuel-library
 https://review.openstack.org/#/c/196114/  that implements
 'compute-vwmare' role (https://mirantis.jira.com/browse/PROD-627) requires
 additional work to do (ceilometer support.), but as far as I can see it
 doesn't affect any other parts of the product.

 We plan to implement it in 3 working days (2 for implementation, 1 day
 for writing system test and test runs), it should not be hard since we
 already support ceilometer compute agent deployment on controller nodes.

 We need 1 DevOps engineer and 1 QA engineer to be engaged for this work.

 So I think it's ok to accept this feature as an exception for feature
 freeze.

 Regards,
 Andrian Noga
 Project manager
 Partner Centric Engineering
 Mirantis, Inc

 Mob.phone: +38 (063) 966-21-24

 Email: an...@mirantis.com
 Skype: bigfoot_ua

 --
 Mike Scherbakov
 #mihgen

 --
 Mike Scherbakov
 #mihgen




-- 
-- 
Regards,
Andrian
Mirantis, Inc

Mob.phone: +38 (063) 966-21-24
Email: an...@mirantis.com
Skype: bigfoot_ua
__
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

[openstack-dev] [fuel] [FFE] FF Exception request for Deploy nova-compute (VCDriver) feature

[Andrian Noga]

Hi,

The patch patch for fuel-library https://review.openstack.org/#/c/196114/
 that implements 'compute-vwmare' role (
https://mirantis.jira.com/browse/PROD-627) requires additional work to
do (ceilometer
support.), but as far as I can see it doesn't affect any other parts of the
product.

We plan to implement it in 3 working days (2 for implementation, 1 day for
writing system test and test runs), it should not be hard since we already
support ceilometer compute agent deployment on controller nodes.

We need 1 DevOps engineer and 1 QA engineer to be engaged for this work.

So I think it's ok to accept this feature as an exception for feature
freeze.

Regards,
Andrian Noga
Project manager
Partner Centric Engineering
Mirantis, Inc

Mob.phone: +38 (063) 966-21-24
Email: an...@mirantis.com
Skype: bigfoot_ua
__
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