date:20170123

Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

2017-01-23 Thread Yujun Zhang

I think it is technically feasible.

We added an experimental trigger for doctor project not long ago[1]. The
trigger is similar to your requirement.

[1]:
https://gerrit.opnfv.org/gerrit/#/c/26839/4/jjb/global/releng-macros.yml


On Tue, Jan 24, 2017 at 12:31 PM Chigang (Justin) 
wrote:

> Hi,
>
> The Command "recheck" is used to run default patch verification again in
> Gerrit.
>
> But there are so many scenarios to be vericated, I think default patch
> verification is not enough.
>
> Is it possible to add a "scenarios" parameters to improve additional
> verification before patch merged in master?
>
> such as :
>
> "recheck odl" will trigged to odl related scenarios.
>
> Thanks
>
> Justin
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

2017-01-23 Thread Chigang (Justin)


Hi,

The Command "recheck" is used to run default patch verification again in 
Gerrit.


But there are so many scenarios to be vericated, I think default patch 
verification is not enough.


Is it possible to add a "scenarios" parameters to improve additional 
verification before patch merged in master?


such as :

"recheck odl" will trigged to odl related scenarios.

Thanks

Justin



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [qtip][yardstick] Q on integration

2017-01-23 Thread Yujun Zhang

Dear all

I reviewed the meeting log[1] and it seems we have several questions to
clarify. Feel free to comment.

1. how to integrate

option 1: as a server like original proposal[2]
option 2: as a module

Both are OK to me, if it is YardStick's team to decide to integrate as a
module, we need to revise the proposal and QTIP will provide full support
on it as well.

2. testing vs benchmarking

For sure benchmarking requires testing data. Benchmarking is one
method/purpose of performance testing. Besides that, we may also use
testing data for verification or validation. You may also use benchmarking
result for verification or validation.

3. benchmarking in YardStick or testing in QTIP

This is not a battle between two projects. We chase different targets and
have common methodology.

QTIP may consume testing data from YardStick but not all of them and not
only from YardStick.

YardStick may use QTIP as benchmarking module or implement its own module.
It's up to YardStick team's decision and I'm fine with either way.

[1]:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-01-24-00.30.log.html

[2]: https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: Reply: [availability] Minutes for HA project weekly meeting on Jan. 18th

2017-01-23 Thread Fu Qiao

Hi, Kanglin. Thank you.
I recall we had ten testcases discussed in the C release, but haven't got all 
of them merged in yardstick, right? We would also like to know your plan about 
these testcases.

-邮件原件-
发件人: Yin Tony [mailto:14_...@tongji.edu.cn] 
发送时间: 2017年1月23日 22:59
收件人: 'Fu Qiao'
抄送: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng Liu'
主题: Reply: [opnfv-tech-discuss] [availability] Minutes for HA project weekly 
meeting on Jan. 18th

Hi Fu Qiao, 

I have to apologize that we don't have any drafts yet for HA test cases in D 
release because recently we are taking efforts on framework improving. We asked 
for a discussion this time in order to know HA team's suggestions on HA test 
cases in D release and then decide what to test.
Before the discussion on test cases , I can share yardstick's current work and 
plan on HA in D release, including some improvements on HA testing and 
yardstick's UI --- grafana, through which we can see test results of yardstick.

-邮件原件-
发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年1月20日 11:13
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: 答复: [opnfv-tech-discuss] [availability] Minutes for HA project weekly 
meeting on Jan. 18th

Hi, all. Below are the minutes for this week's HA project call. Thank you for 
everyone to join the discussion.
We will have our next meeting on Feb. 8th, after the Chinese Lunar New Year 
holidays. And will have Kanglin introduce about the HA test cases in D release.
@Kanglin, do we have drafts about the HA test cases for D release? If yes, 
please send out the link before the meeting so that we can review it at first. 
Thanks.

Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th Minutes Wanghui introduced the 
scope and plan for the Rescuer team. The rescuer team will focus on the date 
pretection issue, currently mainly in VIM. it will use karbor as its upstream 
project, and is intended to collect requirement and gap analysis from the OPNFV 
community. The team has close connection with the OpenStack Karbor project, so 
can be predicted to work closely with the upsteams. Hui also introduced more 
details about the Karbor project in OpenStack.
The plan for the D release is to work out requirement for data pretection. The 
HA team suggested Hui to look into the release doc of the HA project first, and 
see if they can get more clue for the requirement specificly on data 
pretection. The HA requirement doc and scenario analysis doc can help to 
identify requirement and scenarios for data pretection. And  the deployment 
framework doc can help to understand the HA deployment  context when talking 
about data pretection.
fuqiao will send out the release doc to hui after the meeting.

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年1月18日 10:34
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: [opnfv-tech-discuss] [availability] Agenda for HA project weekly meeting on 
Jan. 18th

Hi, all. Below are the agenda for today's HA project meeting. Looking forward 
to talking to you all soon.

Next Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th HA project meeting Please 
join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/772448949   

You can also dial in using your phone.
United States (Long distance):
+1 (646) 749-3117
Access Code: 772-448-949
More phone numbers: https://global.gotomeeting.com/772448949/numbersdisplay.html
Agenda
1 Introduction of Rescuer – Hui Wang
2 Introduction of HA project progress – fuqiao
2 Discussion of co-working between HA and Rescuer




___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss








___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

2017-01-23 Thread Iben Rodriguez

Sure

—
iben.rodrig...@gmail.com
+14087824726
Skype: ibenrodriguez
Twitter: @iben
Wechat: ibentc

> On Jan 23, 2017, at 17:27, Chenshuai  wrote:
> 
> +1
> 
>> 在 2017/1/20 9:38, Weidong.Shao 写道:
>> Hi everyone,
>>  
>> I would like to use this email to express my appreciation to the community 
>> and inform everyone that I will step down as PTL for the Compass4nfv 
>> project. It’s been a privilege serving as PTL for Compass4nfv, one of the 
>> installer tools for OPNFV. I have learned a great deal from the community 
>> members by participating each and every OPNFV Summit as well as many OPNFV 
>> community meetings. Thanks for this amazing journey.
>>  
>> I would also like to nominate Justin Chi from Huawei as the next PTL for 
>> Compass4nfv. Justin has been the technical leader of the Huawei Compass4nfv 
>> open source team in Shanghai, China which consists of many original members 
>> of Compass4nfv. He has demonstrated excellent leadership skills as well as 
>> strong technical skills. Under Justin’s leadership, Compass4nfv has been 
>> extremely active and gained great recognition.
>>  
>> I will be in a fully supportive role to Justin and remain as a Committer to 
>> the Compass4nfv project in the near future.
>>  
>>  
>> We also welcome contributions  to Compass4nfv. 
>> https://wiki.opnfv.org/display/compass4nfv/Compass4nfv.
>>  
>> Compass4nfv project was originally derived from compass project. Official 
>> upstream Compass project had 3 repos, all hosted under openstack.
>> They are:https://github.com/openstack/compass-core
>> https://github.com/openstack/compass-web
>> https://github.com/openstack/compass-adapters
>>  
>> Also we have recently finished the development of containerized  
>>  Compass solution. If you are interested in contributing/knowing more on 
>> this. Contact me weidong.s...@huawei.com or xicheng.cha...@huawei.com
>>  
>> Thanks,
>> Weidong
>> 
>> 
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

2017-01-23 Thread Chenshuai


+1


在 2017/1/20 9:38, Weidong.Shao 写道:


Hi everyone,

I would like to use this email to express my appreciation to the 
community and inform everyone that I will step down as PTL for the 
Compass4nfv project. It’s been a privilege serving as PTL for 
Compass4nfv, one of the installer tools for OPNFV. I have learned a 
great deal from the community members by participating each and every 
OPNFV Summit as well as many OPNFV community meetings. Thanks for this 
amazing journey.


I would also like to nominate Justin Chi from Huawei as the next PTL 
for Compass4nfv. Justin has been the technical leader of the Huawei 
Compass4nfv open source team in Shanghai, China which consists of many 
original members of Compass4nfv. He has demonstrated excellent 
leadership skills as well as strong technical skills. Under Justin’s 
leadership, Compass4nfv has been extremely active and gained great 
recognition.


I will be in a fully supportive role to Justin and remain as a 
Committer to the Compass4nfv project in the near future.


We also welcome contributions  to Compass4nfv. 
https://wiki.opnfv.org/display/compass4nfv/Compass4nfv 
.


Compass4nfv project was originally derived from compass project. 
Official upstream Compass project had 3 repos, all hosted under 
openstack.


They are:https://github.com/openstack/compass-core 



https://github.com/openstack/compass-web 



https://github.com/openstack/compass-adapters 



Also we have recently finished the development of containerized 
Compass solution. If you are interested in contributing/knowing more 
on this. Contact me weidong.s...@huawei.com or xicheng.cha...@huawei.com


Thanks,

Weidong



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

2017-01-23 Thread Beierl, Mark

Hey, Tim.

The original repo has been moving forward: 
https://github.com/codedellemc/puppet-scaleio

Not sure what changes you needed to make, or if they have been superseded by 
changes in the codedellemc repo.  It now claims to support CentOS 6/7, so maybe?

The other repo (https://github.com/cloudscaling/redhat-kvm) has a bunch of 
overcloud scripts that appear to pull in the correct puppet modules and 
configure them.  I wonder if anything from those scripts can be used directly 
in Apex?

Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

> On Jan 23, 2017, at 17:30, Tim Rozet  wrote:
> 
> Hi Mark,
> Back at the previous plugfest in Colorado I had modified scaleio puppet 
> module to work with Apex as a POC.  Not sure if they still work or not, but I 
> never had time to go back and integrate into Apex upstream:
> 
> https://github.com/trozet/puppet-scaleio/tree/rpm_support
> 
> Tim Rozet
> Red Hat SDN Team
> 
> - Original Message -
> From: "Mark Beierl" 
> To: opnfv-tech-discuss@lists.opnfv.org
> Sent: Monday, January 23, 2017 12:38:08 PM
> Subject: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules
> 
> Hello, Apex team, but probably mainly Dan/Tim. 
> 
> At the plugfest, Dan and I chatted briefly about getting ScaleIO puppet 
> modules integrated with Apex. I have noticed that some work has been done by 
> the ScaleIO team in a side repo [1]. Does any of this look like it would be 
> reusable for Apex? 
> 
> [1] https://github.com/cloudscaling/redhat-kvm 
> 
> Regards, 
> Mark 
> 
> Mark Beierl 
> Advisory Solutions Architect 
> Dell EMC | Office of the CTO 
> mobile +1 613 314 8106 
> mark.bei...@dell.com 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

2017-01-23 Thread Tim Rozet

Hi Mark,
Back at the previous plugfest in Colorado I had modified scaleio puppet module 
to work with Apex as a POC.  Not sure if they still work or not, but I never 
had time to go back and integrate into Apex upstream:

https://github.com/trozet/puppet-scaleio/tree/rpm_support

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Mark Beierl" 
To: opnfv-tech-discuss@lists.opnfv.org
Sent: Monday, January 23, 2017 12:38:08 PM
Subject: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

Hello, Apex team, but probably mainly Dan/Tim. 

At the plugfest, Dan and I chatted briefly about getting ScaleIO puppet modules 
integrated with Apex. I have noticed that some work has been done by the 
ScaleIO team in a side repo [1]. Does any of this look like it would be 
reusable for Apex? 

[1] https://github.com/cloudscaling/redhat-kvm 

Regards, 
Mark 

Mark Beierl 
Advisory Solutions Architect 
Dell EMC | Office of the CTO 
mobile +1 613 314 8106 
mark.bei...@dell.com 


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] Danube install help

2017-01-23 Thread Tim Rozet

Hi Bryan,
If the steps I sent you work, then please let me know and I can write up a 
patch to add pxe_wol to Apex.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "BRYAN L SULLIVAN" 
To: "Tim Rozet" 
Cc: opnfv-tech-discuss@lists.opnfv.org
Sent: Monday, January 23, 2017 1:57:53 PM
Subject: RE: [opnfv-tech-discuss] [Apex] Danube install help

Yes, the src reference was an error in my notes. I'll try again with the notes 
you added.

Not supporting PXE_WOL significantly reduces the types of machines that we can 
use for OPNFV development. I recommend that all bare-metal installers consider 
that PXE_WOL may be required, and provide a deploy parameter and hook at the 
proper time so that the PXE_WOL wakeup can be sent by the script to the power 
address (MAC) referenced in the lab config. At the very least if PXE_WOL is 
indicated as the power-type in the lab config, the install script should pause, 
inform the user that they need to wakeup a specific (or all) nodes at that 
time, and proceed when the user hits enter.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Monday, January 23, 2017 7:35 AM
To: SULLIVAN, BRYAN L 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Apex] Danube install help

Hi Bryan,
The package requirements should be the same.  One problem I see from your 
output is you are trying to install source rpms.  The one thing that has 
changed are the network settings format.  We added a lot of comments there so 
hopefully that all makes sense.  To use a single network, just only enable the 
first network in the network settings.  There is no need to use the deprecated 
'--flat' argument anymore.  The deployment will also use a single compute node 
by default.

You can take the latest 4.0 artifacts, they should be stable.

For pxe_wol, you will need to interrupt the deployment and make a couple 
changes as we dont currently support pxe_wol:
1.  add at 
https://github.com/opnfv/apex/blob/master/lib/overcloud-deploy-functions.sh#L289
 :
cat > deploy_command << EOF
openstack overcloud deploy --templates $DEPLOY_OPTIONS --timeout 90 EOF exit 0 
2.  login to undercloud: opnfv-util undercloud 3.  sudo -i; vi 
/etc/ironic/ironic.conf 4.  set enabled drivers: enabled_drivers = 
pxe_ipmitool,pxe_ssh,pxe_drac,pxe_ilo,pxe_wol
5.  systemctl restart openstack-ironic-conductor;exit 6.  cd /home/stack; . 
stackrc; vi instackenv.json (this is your parsed inventory file for OOO) 7.  
for each "pm_type", change it to be "pxe_wol"
8.  for each "pm_addr", change it to be the broadcast address of your ctlplane 
subnet (example 192.0.20/24 would be 192.0.2.255) 9.  add "pm_port", under each 
"pm_addr" and set it to be the dest port for your WOL setup, default is 9 10. 
Set global bash var: dns_server_ext="--nameserver "
11. Do the following commands:
for flavor in baremetal control compute; do
  if openstack flavor list | grep ${flavor}; then
openstack flavor delete ${flavor}
  fi
  openstack flavor create --id auto --ram 4096 --disk 39 --vcpus 1 ${flavor} 
done openstack baremetal import --json instackenv.json openstack baremetal 
configure boot openstack flavor set --property "cpu_arch"="x86_64" --property 
"capabilities:boot_option"="local" baremetal openstack flavor set --property 
"cpu_arch"="x86_64" --property "capabilities:boot_option"="local" --property 
"capabilities:profile"="control" control openstack flavor set --property 
"cpu_arch"="x86_64" --property "capabilities:boot_option"="local" --property 
"capabilities:profile"="compute" compute

neutron subnet-update $(neutron subnet-list | grep -Ev 
"id|tenant|external|storage" | grep -v -- | awk {'print $2'}) 
${dns_server_ext}

12.  cat deploy_command
13.  Copy the output of step 12 and execute in terminal

Ping me on #opnfv-apex if something doesnt work.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "BRYAN L SULLIVAN" 
To: opnfv-tech-discuss@lists.opnfv.org
Sent: Saturday, January 21, 2017 7:41:17 PM
Subject: Re: [opnfv-tech-discuss] [Apex] Danube install help

Also, it’s clear that something has changed re the dependency upon jinja2, 
python-3-ipmi, etc … per the error I got below when trying to install the RPMs: 

--> Processing Dependency: python3-ipmi for package: 
--> opnfv-apex-common-4.0-20170121.noarch

--> Processing Dependency: python3-jinja2 for package: 
--> opnfv-apex-common-4.0-20170121.noarch

--> Finished Dependency Resolution

Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch) 

Requires: python3-jinja2 

Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch) 

Requires: python3-ipmi 

You could try using --skip-broken to work around the problem 

You could try running: rpm -Va --nofiles –nodigest 

[bryan@opnfv apex]$ sudo yum install -y

[opnfv-tech-discuss] Fault Genes WG

2017-01-23 Thread Nematollah Bidokhti

Hi All,

Sorry for sending out many Fault Genes WG meeting invite earlier (and clogging 
your calendars) without a prior email and additional information.

Fault Genes WG https://wiki.openstack.org/wiki/Fault_Genes_Working_Group is 
group focusing on defining the OpenStack fault management policies that can be 
utilized by other OpenStack community projects such as Congress which is 
responsible for executing specific actions.

The intent of this WG is to close the resiliency gap in OpenStack where there 
is no solid foundation on how to handle/mitigate various failure modes. We are 
working on this issue using data from different sources combine with Machine 
Learning (ML) methodology.

We would like to be in a position where OpenStack engineers and operators can 
come to WG wiki and find information on OpenStack faults behavior.

Thanks,

Nemat Bidokhti
Chief Architect, Cloud Resiliency
IT Product Line, Computing Lab
Futurewei Technologies, Inc.
HUAWEI R USA
Tel: +1-408-330-4714
Cell:   +1-408-528-4909
Fax:+1-408-330-5088
E-mail: nematollah.bidok...@huawei.com
2330 Central Expressway
Santa Clara, CA 95050
http://www.huawei.com

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Models Weekly Meeting A

2017-01-23 Thread SULLIVAN, BRYAN L

(glaring error in my notes below, corrected!) You should be able to run these 
tests on Devstack (it previously say "should not" for some freudian reason).

Thanks,
Bryan Sullivan | AT
_
From: SULLIVAN, BRYAN L
Sent: Monday, January 23, 2017 8:53 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: Models Weekly Meeting A

The patch I mentioned on the call (minutes: 
https://wiki.opnfv.org/display/models/Models+Meetings) to the vHello_Tacker.sh 
script and related utilities has been merged: 
https://gerrit.opnfv.org/gerrit/#/c/27355/

You should be able to run this test on a devstack environment (OPNFV 
environment tests are pending). Some notes on that are included in the script 
header. Here are the other notes from the call about it:
*   Devstack environment expectations
*   stable/newton branch deployed
*   Host config recommendations: i7 class CPU, 8-core, 16GB RAM, min 500GB 
disk
*   If running devstack in a VM: use VM parameters 8GB RAM, 20GB disk, 2 
cores, and base the Devstack install on a Newton-supporting OS version e.g. 
Ubuntu Xenial
*   The local.conf I use has been merged as part of the patch: 
https://git.opnfv.org/models/tree/tests/utils/devstack/local.conf
*   The vHello_Tacker.sh test has been updated to put the minimum 
expectations on the host from which you run the test (e.g. no Openstack python 
clients (OSC) need to be installed - all Openstack commands are executed in the 
docker container in which Tacker is running). If you want to run Openstack 
commands directly, you can use the commands:
*   sudo docker attach tacker
*   source /tmp/tacker/admin-openrc.sh (needs to be run only the first time 
you attach)
*   run OSC commands. The clients pre-installed are python-openstackclient 
and python-neutronclient only, You can install others, just note that you may 
need to clone/checkout the stable/newton version, and follow the procedure to 
install as shown in the install_client  function of the tacker-setup.sh script 
(https://git.opnfv.org/models/tree/tests/utils/tacker-setup.sh)
*   You can also run tests via the new utility I created to setup an 
OSC-based test environment using docker: 
https://git.opnfv.org/models/tree/tests/utils/osclient.sh
*   Instructions on how to use osclient.sh are included as comments. This 
script helps isolate the openstack dependencies (python etc) from your host 
machine, which e.g. will be useful if you are testing multiple versions of 
Openstack and don't want to mess up your host, or use virtualenv.

Thanks,
Bryan Sullivan | AT

_
From: SULLIVAN, BRYAN L
Sent: Monday, January 23, 2017 7:58 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Cc: 'Dan Westerberg' >; 
'Tal Barenboim' >; 'Vul, Alex' 
>; 'Henry Fourie' 
>; 'Andrew Veitch' 
>; 
'a...@gigaspaces.com' >; GUPTA, 
ALOK >; 'Ola Liljedahl' 
>; MORTON JR., AL 
>; 'Ulas Kozat' 
>; 'David Suarez Fuentes' 
>; 
'Mario Torrecillas Rodriguez' 
>; 'Ramia, Kannan Babu' 
>; 'Sen, 
Prodip' >; 'Kuppuswamy, Prabu' 
>; DRUTA, DAN 
>; 'Gabor Halász' 
>; 'Seiler, Glenn' 
>; 'S, Deepak' 
>; 'Lawrence Lamers' 
>; 'ramki_krish...@dell.com' 
>; 'Vandris, Steve' 
>; 'yaohelan' 
>; 'Canio Cillis' 
>; 'Shobhan 
AyyadevaraSesha (sayyadev)' >; 
'Trinath Somanchi' >; 
'Zhangyi (ZHANG YI, SCC)' 
>; 'Ahmed Elbornou 
(amaged)' >;

[opnfv-tech-discuss] [Apex] ScaleIO puppet modules

2017-01-23 Thread Beierl, Mark

Hello, Apex team, but probably mainly Dan/Tim.

At the plugfest, Dan and I chatted briefly about getting ScaleIO puppet modules 
integrated with Apex.  I have noticed that some work has been done by the 
ScaleIO team in a side repo [1].  Does any of this look like it would be 
reusable for Apex?

[1] https://github.com/cloudscaling/redhat-kvm

Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Models Weekly Meeting A

2017-01-23 Thread SULLIVAN, BRYAN L

The patch I mentioned on the call (minutes: 
https://wiki.opnfv.org/display/models/Models+Meetings) to the vHello_Tacker.sh 
script and related utilities has been merged: 
https://gerrit.opnfv.org/gerrit/#/c/27355/

You should not be able to run this test on a devstack environment (OPNFV 
environment tests are pending). Some notes on that are included in the script 
header. Here are the other notes from the call about it:
*   Devstack environment expectations
*   stable/newton branch deployed
*   Host config recommendations: i7 class CPU, 8-core, 16GB RAM, min 500GB 
disk
*   If running devstack in a VM: use VM parameters 8GB RAM, 20GB disk, 2 
cores, and base the Devstack install on a Newton-supporting OS version e.g. 
Ubuntu Xenial
*   The local.conf I use has been merged as part of the patch: 
https://git.opnfv.org/models/tree/tests/utils/devstack/local.conf
*   The vHello_Tacker.sh test has been updated to put the minimum 
expectations on the host from which you run the test (e.g. no Openstack python 
clients (OSC) need to be installed - all Openstack commands are executed in the 
docker container in which Tacker is running). If you want to run Openstack 
commands directly, you can use the commands:
*   sudo docker attach tacker
*   source /tmp/tacker/admin-openrc.sh (needs to be run only the first time 
you attach)
*   run OSC commands. The clients pre-installed are python-openstackclient 
and python-neutronclient only, You can install others, just note that you may 
need to clone/checkout the stable/newton version, and follow the procedure to 
install as shown in the install_client  function of the tacker-setup.sh script 
(https://git.opnfv.org/models/tree/tests/utils/tacker-setup.sh)
*   You can also run tests via the new utility I created to setup an 
OSC-based test environment using docker: 
https://git.opnfv.org/models/tree/tests/utils/osclient.sh
*   Instructions on how to use osclient.sh are included as comments. This 
script helps isolate the openstack dependencies (python etc) from your host 
machine, which e.g. will be useful if you are testing multiple versions of 
Openstack and don't want to mess up your host, or use virtualenv.

Thanks,
Bryan Sullivan | AT


_
From: SULLIVAN, BRYAN L
Sent: Monday, January 23, 2017 7:58 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
Cc: 'Dan Westerberg' ; 'Tal Barenboim' 
; 'Vul, Alex' ; 'Henry Fourie' 
; 'Andrew Veitch' ; 
'a...@gigaspaces.com' ; GUPTA, ALOK ; 'Ola 
Liljedahl' ; MORTON JR., AL ; 'Ulas 
Kozat' ; 'David Suarez Fuentes' 
; 'Mario Torrecillas Rodriguez' 
; 'Ramia, Kannan Babu' ; 
'Sen, Prodip' ; 'Kuppuswamy, Prabu' 
; DRUTA, DAN ; 'Gabor Halász' 
; 'Seiler, Glenn' ; 'S, 
Deepak' ; 'Lawrence Lamers' ; 
'ramki_krish...@dell.com' ; 'Vandris, Steve' 
; 'yaohelan' ; 'Canio Cillis' 
; 'Shobhan AyyadevaraSesha (sayyadev)' 
; 'Trinath Somanchi' ; 'Zhangyi 
(ZHANG YI, SCC)' ; 'Ahmed Elbornou (amaged)' 
; 'Randy Levensalor' ; 'Alan 
McNamee' ; 'Tomasini, Lorenzo' 
; 'Daniel Smith' 
; 'Edna Ganon' ; 'Reid Cheng 
(xincheng)' ; 'Pauls, Michael' 
; 'Malla, Malathi' ; 
'Pierre Lynch' 
Subject: RE: Models Weekly Meeting A


Agenda for today is at https://wiki.opnfv.org/display/models/Models+Meetings
Light agenda. I am mostly focused on trying to get Danube support completed 
before the upcoming feature freeze. Likely will not have functest integration 
by then but the basic Hello World test should be compatible with as many 
installers as I have time/resources to verify.
Other topics welcome.

Thanks,
Bryan Sullivan | AT


-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 10:12 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Cc: 'Dan Westerberg'; 'Tal Barenboim'; 'Vul, Alex'; 'Henry Fourie'; 'Andrew 
Veitch'; 'a...@gigaspaces.com'; GUPTA, ALOK; 'Ola Liljedahl'; MORTON JR., AL; 
'Ulas Kozat'; 'David Suarez Fuentes'; 'Mario Torrecillas Rodriguez'; 'Ramia, 
Kannan Babu'; 'Sen, Prodip'; 'Kuppuswamy, Prabu'; DRUTA, DAN; 'Gabor Halász'; 
'Seiler, Glenn';

Re: [opnfv-tech-discuss] Models Weekly Meeting A

2017-01-23 Thread SULLIVAN, BRYAN L

Agenda for today is at https://wiki.opnfv.org/display/models/Models+Meetings
Light agenda. I am mostly focused on trying to get Danube support completed 
before the upcoming feature freeze. Likely will not have functest integration 
by then but the basic Hello World test should be compatible with as many 
installers as I have time/resources to verify.
Other topics welcome.

Thanks,
Bryan Sullivan | AT


-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 10:12 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Cc: 'Dan Westerberg'; 'Tal Barenboim'; 'Vul, Alex'; 'Henry Fourie'; 'Andrew 
Veitch'; 'a...@gigaspaces.com'; GUPTA, ALOK; 'Ola Liljedahl'; MORTON JR., AL; 
'Ulas Kozat'; 'David Suarez Fuentes'; 'Mario Torrecillas Rodriguez'; 'Ramia, 
Kannan Babu'; 'Sen, Prodip'; 'Kuppuswamy, Prabu'; DRUTA, DAN; 'Gabor Halász'; 
'Seiler, Glenn'; 'S, Deepak'; 'Lawrence Lamers'; 'ramki_krish...@dell.com'; 
'Vandris, Steve'; 'yaohelan'; 'Canio Cillis'; 'Shobhan AyyadevaraSesha 
(sayyadev)'; 'Trinath Somanchi'; 'Zhangyi (ZHANG YI, SCC)'; 'Ahmed Elbornou 
(amaged)'; 'Randy Levensalor'; Alan McNamee; Tomasini, Lorenzo; Daniel Smith; 
Edna Ganon; Reid Cheng (xincheng); Pauls, Michael; Malla, Malathi; Pierre Lynch
Subject: Models Weekly Meeting A
When: Monday, January 23, 2017 4:00 PM-5:00 PM (UTC) Coordinated Universal Time.
Where: https://global.gotomeeting.com/join/865421325


Updating this invite to be UTC-based as intended on the wiki, so we limit 
confusion during the seasonal change.

https://wiki.opnfv.org/display/models/Models+Meetings
IRC: #opnfv-models, e.g.  
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-models


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] Danube install help

2017-01-23 Thread Tim Rozet

Hi Bryan,
The package requirements should be the same.  One problem I see from your 
output is you are trying to install source rpms.  The one thing that has 
changed are the network settings format.  We added a lot of comments there so 
hopefully that all makes sense.  To use a single network, just only enable the 
first network in the network settings.  There is no need to use the deprecated 
'--flat' argument anymore.  The deployment will also use a single compute node 
by default.

You can take the latest 4.0 artifacts, they should be stable.

For pxe_wol, you will need to interrupt the deployment and make a couple 
changes as we dont currently support pxe_wol:
1.  add at 
https://github.com/opnfv/apex/blob/master/lib/overcloud-deploy-functions.sh#L289
 :
cat > deploy_command << EOF
openstack overcloud deploy --templates $DEPLOY_OPTIONS --timeout 90
EOF
exit 0
2.  login to undercloud: opnfv-util undercloud
3.  sudo -i; vi /etc/ironic/ironic.conf
4.  set enabled drivers: enabled_drivers = 
pxe_ipmitool,pxe_ssh,pxe_drac,pxe_ilo,pxe_wol
5.  systemctl restart openstack-ironic-conductor;exit
6.  cd /home/stack; . stackrc; vi instackenv.json (this is your parsed 
inventory file for OOO)
7.  for each "pm_type", change it to be "pxe_wol"
8.  for each "pm_addr", change it to be the broadcast address of your ctlplane 
subnet (example 192.0.20/24 would be 192.0.2.255)
9.  add "pm_port", under each "pm_addr" and set it to be the dest port for your 
WOL setup, default is 9
10. Set global bash var: dns_server_ext="--nameserver "
11. Do the following commands:
for flavor in baremetal control compute; do
  if openstack flavor list | grep ${flavor}; then
openstack flavor delete ${flavor}
  fi
  openstack flavor create --id auto --ram 4096 --disk 39 --vcpus 1 ${flavor}
done
openstack baremetal import --json instackenv.json
openstack baremetal configure boot
openstack flavor set --property "cpu_arch"="x86_64" --property 
"capabilities:boot_option"="local" baremetal
openstack flavor set --property "cpu_arch"="x86_64" --property 
"capabilities:boot_option"="local" --property "capabilities:profile"="control" 
control
openstack flavor set --property "cpu_arch"="x86_64" --property 
"capabilities:boot_option"="local" --property "capabilities:profile"="compute" 
compute

neutron subnet-update $(neutron subnet-list | grep -Ev 
"id|tenant|external|storage" | grep -v -- | awk {'print $2'}) 
${dns_server_ext}

12.  cat deploy_command
13.  Copy the output of step 12 and execute in terminal

Ping me on #opnfv-apex if something doesnt work.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "BRYAN L SULLIVAN" 
To: opnfv-tech-discuss@lists.opnfv.org
Sent: Saturday, January 21, 2017 7:41:17 PM
Subject: Re: [opnfv-tech-discuss] [Apex] Danube install help



Also, it’s clear that something has changed re the dependency upon jinja2, 
python-3-ipmi, etc … per the error I got below when trying to install the RPMs: 

--> Processing Dependency: python3-ipmi for package: 
opnfv-apex-common-4.0-20170121.noarch 

--> Processing Dependency: python3-jinja2 for package: 
opnfv-apex-common-4.0-20170121.noarch 

--> Finished Dependency Resolution 

Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch) 

Requires: python3-jinja2 

Error: Package: opnfv-apex-common-4.0-20170121.noarch 
(/opnfv-apex-common-4.0-20170121.noarch) 

Requires: python3-ipmi 

You could try using --skip-broken to work around the problem 

You could try running: rpm -Va --nofiles –nodigest 



[bryan@opnfv apex]$ sudo yum install -y python-jinja2-2.8-5.el7.centos.src.rpm 
python-markupsafe-0.23-9.el7.centos.src.rpm python3-ipmi-0.3.0-1.noarch.rpm 

Loaded plugins: fastestmirror, langpacks 

Loading mirror speeds from cached hostfile 

* base: mirror.hostduplex.com 

* epel: mirrors.kernel.org 

* extras: mirror.scalabledns.com 

* updates: mirrors.kernel.org 

No package python-jinja2-2.8-5.el7.centos.src.rpm available. 

No package python-markupsafe-0.23-9.el7.centos.src.rpm available. 

No package python3-ipmi-0.3.0-1.noarch.rpm available. 

Error: Nothing to do 

[bryan@opnfv apex]$ 




Thanks, 

Bryan Sullivan | AT 





From: SULLIVAN, BRYAN L 
Sent: Saturday, January 21, 2017 4:36 PM 
To: opnfv-tech-discuss@lists.opnfv.org 
Subject: RE: [Apex] Danube install help 




One other thing I forgot in the list added below. 




Thanks, 

Bryan Sullivan | AT 





From: SULLIVAN, BRYAN L 
Sent: Saturday, January 21, 2017 4:33 PM 
To: opnfv-tech-discuss@lists.opnfv.org 
Subject: [Apex] Danube install help 




Hi Apex team, 



I want to get going on installing Apex in a virtual or non-HA/3-node (jumphost, 
control, compute) environment, for Copper, Models, VES. I need to know how the 
install process has changed for Danube, e.g. pre-reqs and command line options. 



Here is the process I used for Colorado virtual install. Is all this still 
correct? 



· sudo yum install -y epel-release 

·

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35791] [releng] Nomination of Markos Chandras as committer to Releng

2017-01-23 Thread Aric Gardner via RT

Hi Fatih

Invite to Markos sent

Regards,
Aric

On Mon, Jan 23, 2017 at 10:18 AM, fatih.degirme...@ericsson.com via RT
 wrote:
>
> Mon Jan 23 10:18:40 2017: Request 35791 was acted upon.
>  Transaction: Ticket created by fatih.degirme...@ericsson.com
>Queue: OPNFV Helpdesk
>  Subject: [releng] Nomination of Markos Chandras as committer to Releng
>Owner: Nobody
>   Requestors: fatih.degirme...@ericsson.com
>   Status: new
>  Ticket https://rt.linuxfoundation.org/Ticket/Display.html?id=35791 >
>
>
> Hi TSC,
>
> Markos Chandras has been voted as new committer to Releng with 10 +2s from 11 
> committers. (Trevor is out of office)
> Here is the link to Gerrit change where the voting took place: 
> https://gerrit.opnfv.org/gerrit/#/c/27167/
>
> Helpdesk,
>
> Please grant Markos committer rights for Releng.
>
> /Fatih
>
> On 2017-01-18, 13:48, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf 
> of Fatih Degirmenci"  fatih.degirme...@ericsson.com> wrote:
>
> Hi Releng Committers,
>
> I would like to nominate Markos Chandras as committer to Releng.
>
> Markos has been one of the main contributors to Cross Community CI 
> activities we have been working on in OPNFV.
> His contributions include but not limited to introducing SuSe support to 
> openstack/bifrost. [1] Thanks to his past (and future) contributions, Cross 
> Community CI will support SuSe on top of Ubuntu and Centos. Apart from making 
> code contributions to upstream, he has been in close contact with OpenStack 
> Infra people to bring OPNFV and OpenStack Infra closer, making OPNFV 
> cummunity visible there for Infra parts as well.
>
> On top of contributing to OpenStack directly in upstream, he also made 
> contributions to OPNFV Releng. [2] One of the contributions I want to 
> highlight is that he stabilized/improved the jobs we use for running patchset 
> verification against openstack/bifrost patches upstream, making it possible 
> for us to start discussions with Bifrost PTL to get the voting rights for 
> OPNFV for openstack/bifrost which is a great first step towards future. [2]
>
> Please cast your vote on Gerrit: 
> https://gerrit.opnfv.org/gerrit/#/c/27167/
>
> I'll close the vote on 2017-01-2017.
>
> [1] https://review.openstack.org/#/q/owner:mchandras%2540suse.de
> [2] https://gerrit.opnfv.org/gerrit/#/q/owner:%22Markos+Chandras%22
>
> /Fatih
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
>

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Reply: [availability] Minutes for HA project weekly meeting on Jan. 18th

2017-01-23 Thread Yin Tony

Hi Fu Qiao, 

I have to apologize that we don't have any drafts yet for HA test cases in D 
release because recently we are taking efforts on framework improving. We asked 
for a discussion this time in order to know HA team's suggestions on HA test 
cases in D release and then decide what to test.
Before the discussion on test cases , I can share yardstick's current work and 
plan on HA in D release, including some improvements on HA testing and 
yardstick's UI --- grafana, through which we can see test results of yardstick.

-邮件原件-
发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年1月20日 11:13
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: 答复: [opnfv-tech-discuss] [availability] Minutes for HA project weekly 
meeting on Jan. 18th

Hi, all. Below are the minutes for this week's HA project call. Thank you for 
everyone to join the discussion.
We will have our next meeting on Feb. 8th, after the Chinese Lunar New Year 
holidays. And will have Kanglin introduce about the HA test cases in D release.
@Kanglin, do we have drafts about the HA test cases for D release? If yes, 
please send out the link before the meeting so that we can review it at first. 
Thanks.

Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th Minutes Wanghui introduced the 
scope and plan for the Rescuer team. The rescuer team will focus on the date 
pretection issue, currently mainly in VIM. it will use karbor as its upstream 
project, and is intended to collect requirement and gap analysis from the OPNFV 
community. The team has close connection with the OpenStack Karbor project, so 
can be predicted to work closely with the upsteams. Hui also introduced more 
details about the Karbor project in OpenStack.
The plan for the D release is to work out requirement for data pretection. The 
HA team suggested Hui to look into the release doc of the HA project first, and 
see if they can get more clue for the requirement specificly on data 
pretection. The HA requirement doc and scenario analysis doc can help to 
identify requirement and scenarios for data pretection. And  the deployment 
framework doc can help to understand the HA deployment  context when talking 
about data pretection.
fuqiao will send out the release doc to hui after the meeting.

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年1月18日 10:34
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: [opnfv-tech-discuss] [availability] Agenda for HA project weekly meeting on 
Jan. 18th

Hi, all. Below are the agenda for today's HA project meeting. Looking forward 
to talking to you all soon.

Next Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th HA project meeting Please 
join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/772448949   

You can also dial in using your phone.
United States (Long distance):
+1 (646) 749-3117
Access Code: 772-448-949
More phone numbers: https://global.gotomeeting.com/772448949/numbersdisplay.html
Agenda
1 Introduction of Rescuer – Hui Wang
2 Introduction of HA project progress – fuqiao
2 Discussion of co-working between HA and Rescuer




___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss





___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [releng] Nomination of Markos Chandras as committer to Releng

2017-01-23 Thread Fatih Degirmenci

Hi TSC,

Markos Chandras has been voted as new committer to Releng with 10 +2s from 11 
committers. (Trevor is out of office)
Here is the link to Gerrit change where the voting took place: 
https://gerrit.opnfv.org/gerrit/#/c/27167/

Helpdesk,

Please grant Markos committer rights for Releng.
 
/Fatih

On 2017-01-18, 13:48, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
Fatih Degirmenci"  wrote:

Hi Releng Committers,

I would like to nominate Markos Chandras as committer to Releng.

Markos has been one of the main contributors to Cross Community CI 
activities we have been working on in OPNFV. 
His contributions include but not limited to introducing SuSe support to 
openstack/bifrost. [1] Thanks to his past (and future) contributions, Cross 
Community CI will support SuSe on top of Ubuntu and Centos. Apart from making 
code contributions to upstream, he has been in close contact with OpenStack 
Infra people to bring OPNFV and OpenStack Infra closer, making OPNFV cummunity 
visible there for Infra parts as well. 

On top of contributing to OpenStack directly in upstream, he also made 
contributions to OPNFV Releng. [2] One of the contributions I want to highlight 
is that he stabilized/improved the jobs we use for running patchset 
verification against openstack/bifrost patches upstream, making it possible for 
us to start discussions with Bifrost PTL to get the voting rights for OPNFV for 
openstack/bifrost which is a great first step towards future. [2]

Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/27167/

I'll close the vote on 2017-01-2017.

[1] https://review.openstack.org/#/q/owner:mchandras%2540suse.de
[2] https://gerrit.opnfv.org/gerrit/#/q/owner:%22Markos+Chandras%22

/Fatih

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

2017-01-23 Thread Chigang (Justin)


Hi Weidong,

Thanks for Weidong's nomination and support.

After I joined into the OPNFV community, I learned a lot from the OPNFV, 
including the knowledge of many upstream communities. I am very honored 
to be the PTL Compass4NFV project.


Weidong and I has made an anquaintance in OPNFV, he is an excellent PTL 
and lead us make a great achievement in the past OPNFV release. I 
learned a lot from him, more than technology, management.


Compass4NFV will be more focused on the community development in the 
future release, especially in cooperation with other projects.


Recently the Compass4NFV evolution plan will be announced, anyone 
interested is welcome to contribute.


Best Regards

Justin

在 2017/1/21 2:17, Yingjun Li 写道:


+1

*From:*opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of 
*Ulrich Kleber

*Sent:* Friday, January 20, 2017 12:47 AM
*To:* Weidong.Shao; opnfv-tech-discuss@lists.opnfv.org >> 
'opnfv-tech-discuss@lists.opnfv.org'; Chigang (Justin)

*Subject:* Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

+1

*From:*opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of 
*Weidong.Shao

*Sent:* Friday, 20 January, 2017 02:38
*To:* opnfv-tech-discuss@lists.opnfv.org >> 
'opnfv-tech-discuss@lists.opnfv.org'; Chigang (Justin)

*Subject:* [opnfv-tech-discuss] Compass4nfv PTL nomination

Hi everyone,

I would like to use this email to express my appreciation to the 
community and inform everyone that I will step down as PTL for the 
Compass4nfv project. It’s been a privilege serving as PTL for 
Compass4nfv, one of the installer tools for OPNFV. I have learned a 
great deal from the community members by participating each and every 
OPNFV Summit as well as many OPNFV community meetings. Thanks for this 
amazing journey.


I would also like to nominate Justin Chi from Huawei as the next PTL 
for Compass4nfv. Justin has been the technical leader of the Huawei 
Compass4nfv open source team in Shanghai, China which consists of many 
original members of Compass4nfv. He has demonstrated excellent 
leadership skills as well as strong technical skills. Under Justin’s 
leadership, Compass4nfv has been extremely active and gained great 
recognition.


I will be in a fully supportive role to Justin and remain as a 
Committer to the Compass4nfv project in the near future.


We also welcome contributions  to Compass4nfv. 
https://wiki.opnfv.org/display/compass4nfv/Compass4nfv 
.


Compass4nfv project was originally derived from compass project. 
Official upstream Compass project had 3 repos, all hosted under 
openstack.


They are:https://github.com/openstack/compass-core 



https://github.com/openstack/compass-web 



https://github.com/openstack/compass-adapters 



Also we have recently finished the development of containerized 
Compass solution. If you are interested in contributing/knowing more 
on this. Contact me weidong.s...@huawei.com 
 or xicheng.cha...@huawei.com 



Thanks,

Weidong

. 


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

[opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

[opnfv-tech-discuss] [qtip][yardstick] Q on integration

[opnfv-tech-discuss] 答复: Reply: [availability] Minutes for HA project weekly meeting on Jan. 18th

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

Re: [opnfv-tech-discuss] [Apex] Danube install help

[opnfv-tech-discuss] Fault Genes WG

Re: [opnfv-tech-discuss] Models Weekly Meeting A

[opnfv-tech-discuss] [Apex] ScaleIO puppet modules

Re: [opnfv-tech-discuss] Models Weekly Meeting A

Re: [opnfv-tech-discuss] Models Weekly Meeting A

Re: [opnfv-tech-discuss] [Apex] Danube install help

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35791] [releng] Nomination of Markos Chandras as committer to Releng

[opnfv-tech-discuss] Reply: [availability] Minutes for HA project weekly meeting on Jan. 18th

[opnfv-tech-discuss] [releng] Nomination of Markos Chandras as committer to Releng

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

19 matches

Site Navigation

Mail list logo

Footer information