date:20170404

Re: [opnfv-tech-discuss] [vsperf] Trying PROX

2017-04-04 Thread Cooper, Trevor

I just tried it and works … we can discuss in the meeting tomorrow

/Trevor



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of MORTON, ALFRED 
C (AL)
Sent: Tuesday, April 04, 2017 2:51 PM
To: Pervaze Akhtar 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [vsperf] Trying PROX

Thanks for your suggestion Pervaze!
I tried a command from history that seemed to do the trick.

I encountered some additional errors, but dug some more
and found the missing setup steps.

I documented our little adventure on the etherpad:
https://etherpad.opnfv.org/p/vsperfpdv

Al

From: Pervaze Akhtar [mailto:pervaze.akh...@netronome.com]
Sent: Tuesday, April 04, 2017 3:58 PM
To: MORTON, ALFRED C (AL)
Subject: Re: [opnfv-tech-discuss] [vsperf] Trying PROX

> but no mounted hugetlbfs found for that size

The command to mount the hugepagesfs is roughly:
mount -t hugetlbfs none /mnt/hugetlbfs
The error looks like you (or the app) is using DPDK and the run time env. is 
trying to allocate hugepages, but either the they are not mounted, or the grub 
or other settings are not allocating the expected number of hugepages (looks 
like 1G pages in this case).

On Tue, Apr 4, 2017 at 3:45 PM, MORTON, ALFRED C (AL) 
mailto:acmor...@att.com>> wrote:
Hi all,

As the plugfest is coming soon, I made a few minutes
to try-out PROX, which we discussed earlier this year.

Although prox seems to run fine on Pod 12 Node-5,
the Node-4 version is currently throwing this error:

EAL: 59 hugepages of size 1073741824 reserved, but no mounted hugetlbfs found 
for that size
PANIC in rte_eal_init():
Cannot get hugepage information

helpful clues appreciated,
Al

___
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] [vsperf] Summit CFP - VSPERF submission

2017-04-04 Thread Cooper, Trevor

Submission deadline is Monday, April 10


The Design Summit takes place June 12-13 and is where the OPNFV technical 
community will convene to continue working on the E-Release and have plenary 
sessions and project breakouts. It is very focused on the OPNFV platform. The 
Summit Conference takes place Jun 14-15 and is for the wider NFV ecosystem, 
featuring keynotes, breakout sessions, a technology showcase, networking 
opportunities, etc. This is where the breakouts will be structured into the six 
tracks. Panels consist of 4 or more speakers in a single session. When in 
doubt, we recommend you submit for the Summit conference as a breakout session. 
From there, our track chairs will be able to make further recommendations as 
needed.

---

Let's submit at least one VSPERF submission ... give your suggestions to 
edit/update this proposal ... and/or make a new proposal ... the more the 
better ... once reviewed the organizers can recommend to combine proposals if 
there is overlap.

Title: ???
Speakers: Trevor, ... who else is interested?
Abstract

VSPERF is an automated test-framework for measuring NFVI data-plane performance 
using industry standard benchmark specifications and is used by open source 
development teams as well as commercial vendors. The VSPERF team's experience 
includes publishing an IETF internet draft and deploying a CI test environment 
with multiple traffic generators and DUT configurations. This session will go 
deep into how VSPERF can be used to optimize and improve data-plane performance 
of NFVI as well as provide data driven comparisons between hardware and 
software traffic generators and capabilities.


-

We decided to submit some proposals from the test working group ...  
https://etherpad.opnfv.org/p/TestCommunitySummit. Proposals from individuals 
and test projects are still encouraged!



Title: OPNFV Plugfest Unplugged

Speakers: Trevor and ?

The OPNFV Testing Working Group aims to unify testing strategies and methods 
across projects and test infrastructure. Plugfests (held after each release)  
have greatly assisted with this effort and helped shape the evolution of our 
testing community. This session provides an insider's view into OPNFV Plugfests 
explaining participation options, benefits and learnings from three successful 
events to-date. We will also discuss how Plugfest results have impacted 
evolution of test strategies for various types of testing including VNF and 
Stress testing.





Title: Conversations with the testing community

Panel discussion: Jose, Yujun, Kubi, Trevor, Gabriel, Mark

Moderator: Morgan

Abstract:

After a brief introduction of the activities of each project, some questions 
will help the audience to understand the work of the testing groups.

How can we contribute to a test project?

Can I create my test project or shall I join an existing one?

How do you work concretely? How do you interact with infra group, feature 
projects?

What are the collaborative work across the projects?

Is there a strategy for the test coverage, for the stress tests?

How are defined the test categories?

What are the main challenges for the future?





Title: test community what's next?

speakers: Kubi or Jack/Gabriel/Morgan

Abstract

The testing community defined priorities for Danube.

We worked on a landing page (in progress) and test case catalogue (hopefully 
available for Danube)

The test projects already consume test database API and created internal API.

Storperf API is used by Yardstick. Dovetail calls Functest and Yardstick. 
Bottleneck uses yardstick API.

Each test project may expose and consume APIs from other test projects and 
could also be used by other projects.

The goal of this session is to remind the first collaborative achievements and 
see how the testing community could adopt a micro services approach in order to 
harmonize the way to expose and consume API to others





Title: Big Data for Testing

Speakers: Donald Hunter (donaldh) , Yujun Zhang (ZTE) 
zhangyujun+...@gmail.com

Abstract

The testing community created tens of testing projects, hundreds of testing 
cases, thousands of test jobs.

Huge amount of testing data has been produced. What comes next, then?

The testing community put in place tools and procedures to declare 
testcases/projects, normalize and upload results.

These tools and procedures have been adopted so we now have lots of data 
covering lots of scenarios, hardware, installers.



In this presentation, we shall discuss the stakes and challenges of result post 
processing.

How analytics can provide valuable inputs to the community, end users or 
upstream projects.

How can we produce accurate indicators, reports and graphs, focus on 
interpreting / consuming test results.

How can we get the best of breeds of our result mine?


/Trevor

--- Begin Message ---

If you are having trouble viewing this email, try viewing it in a 
browser

[opnfv-tech-discuss] OpenRetriever Project Meeting

2017-04-04 Thread jiaxuan

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 16.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN=opnfv-tech-discuss@lists.opnfv.org;RSVP=TRUE:mailto:opnfv-tech-
	disc...@lists.opnfv.org
CLASS:PUBLIC
CREATED:20170405T024534Z
DESCRIPTION:\nAs the holiday in China\, we are going to change the meeting 
	time to April 7th.\n\nOpenRetriever is a project to integrate container in
	to NFV. Meeting Time is 09:00-9:30 a.m. UTC on  April 7th. \n\nAgenda:\n1.
	   OpenRetriever Release Plan \n  1) Openretriever installer  (fuel or
	 JOID\, openstack + kubernetes with kuryr-kubernete)\n  2) Investigate
	 integration between MANO (ONAP) & kubernetes \n  3) Investigate integ
	ration between kubernetes & kuryr-kubernetes (openstack project) & OVS wit
	h DPDK \n  4) Investigate multi-network for kubernetes PODs \n  5)
	Yardstick & Function & Performance Test for openretriever \n  6)Openre
	triever scenarios \n  7)Openretriever CI \n  8) Openretriever docu
	ment\n2.  Container network discussion for NFV. (NetReady) 3.  How NGVS is
	 working with OR ?\n\n•  OpenRetriever Page:  https://wiki.opnfv.org
	/display/OpenRetriever/OpenRetriever\n\n•  Etherpad: https://etherpa
	d.opnfv.org/p/openretriever  (Write down what you want to talk about)\n\n
	•  IRC channel:  #opnfv-container\n\n•  Join:  Go to https://z
	oom.us/j/6665521139  \n
DTEND;TZID="China Standard Time":20170407T173000
DTSTAMP:20170405T024534Z
DTSTART;TZID="China Standard Time":20170407T17
LAST-MODIFIED:20170405T024534Z
ORGANIZER;CN=jiaxuan:mailto:jiax...@chinamobile.com
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=en-us:OpenRetriever Project Meeting
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E008D02BB4DEF8ADD201000
	010002BA88A244801D3419C7213A75978737D
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR



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

[opnfv-tech-discuss] [opnfv-tech-discussion][availability][doctor]Discussion of HA API with the doctor team

2017-04-04 Thread Fu Qiao

Hi, Ryota.
As you may have noticed, the HA team has been working on the HA API work during
the D release. We had a proposal worked out for the release. Since the scheme
we proposed has close relationship with the doctor scheme, we would like to
discuss further with the doctor team to make sure we can have a unified
solution.
You can find detailed proposal as below. I wonder if your team is OK to join
the next HA project meeting on Apr. 12, at 13:00-14:00 UTC? Thank you!

http://docs.opnfv.org/en/stable-danube/submodules/availability/docs/development/overview/index.html

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年4月5日 10:28
收件人: greg.wai...@windriver.com; opnfv-tech-discuss@lists.opnfv.org; 'Yin Tony';
'juan_qiu'
抄送: 'Edgar StPierre'; 'Hui Wang'; 'Yue Yuan'; mano...@lists.opnfv.org
主题: [opnfv-tech-discuss] 答复: [opnfv-tech-discussion][availability]project
meeting on Mar. 29

Hi, all. Below are the minutes for our call last week. Sorry for the delay due
to the holiday in China. Thank you to everyone for the discussion.

Minutes
HA API doc updates – Greg
The team goes through the update version. Some members of the MANO WG join the
discussion and provide useful suggestions. Detailed suggestions are as follows:
1) The team agrees to restructure the doc as a proposal, not a total solution.
2) Michael, from the MANO WG, indicates that currently there are more than one
framework to improve the availability and reliability of the OPNFV Platform,
which could be a good thing. However coordination work is needed in order to
tell people how to behave in a unified way.
3) priority should be defined among multiple schemes to avoid race condition
4) The team agrees to include the heart beat part and peer state notification
session for the D release.
5) It is suggested to continue the discussion of the proposal with the
parameter team and doctor team.

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年3月28日 14:41
收件人: greg.wai...@windriver.com; opnfv-tech-discuss@lists.opnfv.org; 'Yin Tony';
'juan_qiu'
抄送: 'Edgar StPierre'; 'Hui Wang'; 'Yue Yuan'
主题: [opnfv-tech-discuss] [opnfv-tech-discussion][availability]project meeting
on Mar. 29

Hi, Greg. Thank you for the update.
I arrange another meeting tomorrow on Mar. 29th to continue the discussion. I
suggest we go through the heartbeat section first and see if we can reach an
agreement.

Meetings for High Availability Project
Next Meeting on 13:00-14:00 UTC, Wednesday, Mar. 29th
https://global.gotomeeting.com/join/772448949

Toll free NO.
USA: +1 (646) 749-3117

Meeting ID: 772-448-949
Agenda
HA API doc updates – Greg

-邮件原件-
发件人: Greg Waines (OPNFV Code Review) [mailto:ger...@opnfv.org]
发送时间: 2017年3月28日 0:36
抄送: Ulrich Kleber; Hui Wang; Stefan Arntzen; Qiao Fu; Ian Jolliffe; Edgar
StPierre; Yue Yuan
主题: Change in availability[master]: Updating Commit based on third round of
review during OPNFV ...

Greg Waines has posted comments on this change. (
https://gerrit.opnfv.org/gerrit/26663 )

Change subject: Updating Commit based on third round of review during OPNFV HA
meetings, as well as submitted comments on the review.
..

Patch Set 4:

(11 comments)

Updated based on recent comments.
And added HTML and PDF versions of document for easier reading.

https://gerrit.opnfv.org/gerrit/#/c/26663/4/Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst
File Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst:

PS4, Line 15: bstract: This document provides an overview of a set of new
:optional capabilities where the OpenStack Cloud messages
:into the Guest VMs in order to provide improved Availability
:of the hosted VMs. These new capabilities include: enabling
:the detection of and recovery from internal VM faults,
enabling
:Guest VMs to gracefully handle and provide loss-of-service
:warnings to cloud adminstrative operations on the VM and
:providing a simple out-of-band messaging service to prevent
:scenarios such as split brain.
> Hi, Greg. You may find more info in the following link.
Ugh ... couldn't figure out how to do it from these instructions.

I generated an HTML version and PDF version and included it in COMMIT along
with the .rst file.

PS4, Line 42: VM Heartbeating and Health Checking
: - VM Event Notification and Feedback
: - VM Peer State Notification and Messaging
> Good to hear. I think we should not merge this patch without this being doc
I added more explicit indication in the INTRODUCTION that VNFM interactions
were discussed in the specific sections.

AND in the VM Event Notificat

[opnfv-tech-discuss] 答复: [opnfv-tech-discussion][availability]project meeting on Mar. 29

2017-04-04 Thread Fu Qiao

Hi, all. Below are the minutes for our call last week. Sorry for the delay due
to the holiday in China. Thank you to everyone for the discussion.

Meetings for High Availability Project
Next Meeting on 13:00-14:00 UTC, Wednesday, Mar. 29th
https://global.gotomeeting.com/join/772448949

Toll free NO.
USA: +1 (646) 749-3117

Meeting ID: 772-448-949
Agenda
HA API doc updates – Greg

Greg Waines has posted comments on this change. (
https://gerrit.opnfv.org/gerrit/26663 )

Change subject: Updating Commit based on third round of review during OPNFV HA
meetings, as well as submitted comments on the review.
..

Patch Set 4:

(11 comments)

Updated based on recent comments.
And added HTML and PDF versions of document for easier reading.

https://gerrit.opnfv.org/gerrit/#/c/26663/4/Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst
File Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst:

I generated an HTML version and PDF version and included it in COMMIT along
with the .rst file.

AND in the VM Event Notification and Feedback section, i added a note at the
beginning discussing the open item that this currently solicits feedback from
VM and notifies VM of upcoming command 'independent' of VNFM. i.e. even for
commands issued by the VNFM, this service provides an optional check on the
state of the VM and a Notification to the VM for graceful handling of the
command. An alternative approach would be to go thru the VNFM to both check
the state of the VM and notify the VM of the event. More discussion is
required here with the Management and Orchestration OPNFV Team.

PS4, Line 51: lifecycle of the VM
> I think the host-to-guest message cannot be earlier than the VNFM having st
I changed the wording to say
"... is available very early after spawning the VM."

There is not intent for host-to-guest VM messaging to be used for high-level VM
lifecycle management.

The intent of the sentence is to say that the messaging mechanism is quite
simple and therefore can be available v

[opnfv-tech-discuss] [mano-wg] OPNFV D 1.0 MANO review and D/E TOSCA for Scenario, API + usecase discussions Meeting #25

2017-04-04 Thread Prakash Ramchandran

Hi all,

Please join MANO WG Meeting#25 this Wednesday April 5
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

1.Agenda Bashing

2. Q1 MANO WG 
report
 - Prakash

3. TOSCA for MANO scenario descriptor file from last week discussions - Bryan/ 
Narinder/ Uli

4. testing vIMS feedback from test WG - Bryan/Prakash on review in Test WG, 
Orchestra (Giuseppe), Yingjun Li(Opera),

5. Considerations for lower complexity  SBC use case based on 3-node vHello 
Tacker in Models Project (Bryan/Aimee)

6. Anything new from ONS summit at Santa Clara (April 3-6) - OPNFV Release D1.0 
news and anything on ONAP?

7. Any follow-up  from MANO WG teams like WSO2 API and  for 
Events  Plugfest (Paris),  OpenStack 
Boston + OPNFV Beijing Summit.

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

[opnfv-tech-discuss] [Update] OPNFV Release Meeting (ASIA) - IRC Only

2017-04-04 Thread dmcbride

Reminder - OPNFV APAC release meeting today at 7:30 pm (Pacific).  That's  
02:30 UTC, or for example, 10:30 a.m. in Beijing.


You have been invited to the following event.

Title: OPNFV Release Meeting (ASIA) - IRC Only
This meeting is intended for OPNFV members in Asia who are unable to attend  
the regular release meeting.  We will meet every two weeks on IRC.


Please join me to discuss status, process, and to resolve issues related to  
OPNFV releases.  Questions welcome!

When: Tue Apr 4, 2017 7:30pm – 8pm Pacific Time
Where: IRC channel:  OPNFV-Release
Who:
* dmcbr...@linuxfoundation.org - organizer
* kong.w...@zte.com.cn
* opnfv-project-le...@lists.opnfv.org
* Zhipeng Huang
* zhangyujun+...@gmail.com
* r-m...@cq.jp.nec.com
* joehu...@huawei.com
* chig...@huawei.com
* hu.zhiji...@zte.com.cn
* hu@zte.com.cn
* huangzhip...@huawei.com
* jean.gaoli...@huawei.com
* fuq...@chinamobile.com
* gabriel.yuy...@huawei.com
* zhang.yuj...@zte.com.cn
* opnfv-tech-discuss@lists.opnfv.org
* Jason HU
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Trying PROX

2017-04-04 Thread MORTON, ALFRED C (AL)

Thanks for your suggestion Pervaze!
I tried a command from history that seemed to do the trick.

I encountered some additional errors, but dug some more
and found the missing setup steps.

I documented our little adventure on the etherpad:
https://etherpad.opnfv.org/p/vsperfpdv

Al

From: Pervaze Akhtar [mailto:pervaze.akh...@netronome.com]
Sent: Tuesday, April 04, 2017 3:58 PM
To: MORTON, ALFRED C (AL)
Subject: Re: [opnfv-tech-discuss] [vsperf] Trying PROX

> but no mounted hugetlbfs found for that size

The command to mount the hugepagesfs is roughly:
mount -t hugetlbfs none /mnt/hugetlbfs
The error looks like you (or the app) is using DPDK and the run time env. is 
trying to allocate hugepages, but either the they are not mounted, or the grub 
or other settings are not allocating the expected number of hugepages (looks 
like 1G pages in this case).

On Tue, Apr 4, 2017 at 3:45 PM, MORTON, ALFRED C (AL) 
mailto:acmor...@att.com>> wrote:
Hi all,

As the plugfest is coming soon, I made a few minutes
to try-out PROX, which we discussed earlier this year.

Although prox seems to run fine on Pod 12 Node-5,
the Node-4 version is currently throwing this error:

EAL: 59 hugepages of size 1073741824 reserved, but no mounted hugetlbfs found 
for that size
PANIC in rte_eal_init():
Cannot get hugepage information

helpful clues appreciated,
Al

___
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] [vsperf] Trying PROX

2017-04-04 Thread MORTON, ALFRED C (AL)

Hi all,

As the plugfest is coming soon, I made a few minutes
to try-out PROX, which we discussed earlier this year.

Although prox seems to run fine on Pod 12 Node-5,
the Node-4 version is currently throwing this error:

EAL: 59 hugepages of size 1073741824 reserved, but no mounted hugetlbfs found 
for that size
PANIC in rte_eal_init():
Cannot get hugepage information

helpful clues appreciated,
Al

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

[opnfv-tech-discuss] OPNFV Danube Announced Today

2017-04-04 Thread Brandon Wick

OPNFV Technical Community:

Today, we went live with OPNFV's fourth Release -- Danube. Thank you to
everyone in the community who helped to achieve this major milestone. The
press release and eblast went out this morning and articles from industry
pubs are going live. Here's a an article from Carol Wilson at Light Reading

.

Listed below are links to more information. For those on social media, we
encourage you to help spread the word about Danube by making original posts
(with #OPNFVDanube) and sharing/re-tweeting the Danube updates from the
OPNFV social channels today and throughout the week.

Danube Press Release

Danube Landing Page 
Danube Blog Post

Danube Infographic


Best,

Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org

*OPNFV Summit CFP closes April 10!
*
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Congress on TryStack?

2017-04-04 Thread Will Foster


On 23/03/17 13:49 -0400, Dan Radez wrote:

  Brian,
  I've copied our guys that work on TryStack: Will and Kambiz.

  They will be able to give you an update on when it will be updated to a
  newer version of OpenStack.

  As far as installing Congress, I would imaging they wouldn't have a
  problem deploying it. Although RDO doesn't have congress support until
  Ocata so this wouldn't be an option until they are able to move to
  Ocata.

  Dan

  On 03/22/2017 07:13 PM, SULLIVAN, BRYAN L wrote:

  Tim, Dan, Dave (RedHatters):


  Do you know if we can add more OpenStack services to TryStack
  ([1]http://trystack.org/)? I’m investigating for the Congress team
  whether it could be a useful test environment for those that want to
  test out Congress.


  Also, seems it’s based upon Liberty. Any idea when it will get updated
  to Newton?


  Thanks,

  Bryan Sullivan | AT&T



Hi Folks,

Trystack.org is currently in a holding pattern on OpenStack upgrades
(to Ocata or later) until we can get a working multi-auth replacement
for Facebook OAuth authentication.

There's around 30,000 accounts on the Trystack OpenStack
implementation and around 6,000 active users with frequent signups so
we absolutely need gated, self-service account signups that supports a
common identity provider.  Due to changes in Horizon and our long-term
intention of moving off Facebook for auth we're not investing
development time into maintaining the facebook-horizon-django
integration[1] bridge which has stopped working in Mitaka and beyond.

We don't have an ETA yet, we've been in discussions with the OpenStack
upstream infrastructure folks and it's an agenda item on their weekly
meetings (as they need similiar functionality in place for some of
their services).

It's on our radar but we also have a small (2-person) team doing all
the administration and development of Trystack at the moment.  I hope
to have more updates soon after syncing with the OpenStack upstream
infra group and I can update folks on this thread if it's the best
place.

So far as Congress goes and any other ancillary OpenStack components
we're happy to do so if it's shipped with RDO or working with any of
the teams to get it up and running if people want to use it.  This
won't happen until the upgrade to Ocata and beyond however.

[1] - https://github.com/trystack/python-django-horizon-facebook

Thanks,

-will

--
Will Foster
Engineering R&D ⛅ Red Hat, Inc.
⚓ wfoster ✎ hobo.house ⚿ 07BC7E81


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

Re: [opnfv-tech-discuss] [functest] Security Scanning

2017-04-04 Thread Luke Hinds

On Mon, Apr 3, 2017 at 6:45 PM, SULLIVAN, BRYAN L  wrote:

> Security scanning is very important, and I would like to extend it to open
> source license scanning, etc. this should be part of CI and Functest. Let's
> talk about how we can keep this group and its work moving forward.
>
>
Hi Bryan,

That's still on as an another project, its confusing as it has similar
name, but its different. This email is around scanning OpenStack hosts to
view levels of hardening compliance which is a scenario used in functest.
The other project with Infra-WG is around gate scanning content and code. I
don't blame the mix up on you, its from me using confusing naming
conventions :)

Cheers,

Luke


> On Apr 3, 2017, at 9:46 AM, Jose Lausuch 
> wrote:
>
> Hi Luke,
>
>
>
> We should of course keep your test case and if you had time or anyone who
> wants to take it, we could try to make it run on other installers as well.
> We have now an abstraction layer to connect to the deployed nodes
> regardless of the installer, we could probably adapt the code to use it and
> make it “installer agnostic”.  There are also a few things I’d like to
> expect from the test case as Functest has evolved, it would be great that
> the test case adapts to it.
>
>
>
> How will be your availability for Euphrates? If you don’t have much time
> maybe we could propose it as an intern project.
>
>
>
> Regards,
>
> Jose
>
>
>
>
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> ] *On Behalf Of *Luke Hinds
> *Sent:* Monday, April 03, 2017 09:36 AM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] [functest] Security Scanning
>
>
>
> Hi Functest'ers,
>
>
>
> I am aware I have not been as active on security scanning as I originally
> hoped, largely due to being v-busy working on upstream. I have also not
> seen much uptake in contributions from others or any requests for support
> or enhancements to make from operators / users of OPNFV.
>
>
>
> With the above snippet in mind, would you like to revisit the projects use
> in functest? I am not saying I wish to decommission, as I put quite a good
> number of hours into the code, but at the same time I am aware my
> contributions have not been very active and I am not sure if that will
> change in the foreseeable future. You might see otherwise and like to
> enhance it further, so it seems a discussion could be worthwhile.
>
>
>
> If you would like we could have this as a topic on a functest meeting or
> alternately I will be at the plugfest too.
>
>
>
> Cheers,
>
>
>
> Luke
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss&d=DwICAg&c=LFYZ-o9_
> HUMeMTSQicvjIg&r=OrbtGCluczz9awEKz9Fv7g&m=kulwm6e5kj6VDwhnBiUYW0jmoTZpEY
> 657zJRJ1KSQcE&s=_sqLQE-MQAleJ1L7Vn-4WI_egkjCXLnih6PhuZLkyzM&e=
>



-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [functest] Security Scanning

2017-04-04 Thread Luke Hinds

Hi Jose,

That's good to hear. The intern idea sounds very good. For E release its
looking very busy for me, but I would completely support anyone trying to
grok the existing code and be prompt in reviewing / merging any changes.

Cheers,

Luke

On Mon, Apr 3, 2017 at 5:46 PM, Jose Lausuch 
wrote:

> Hi Luke,
>
>
>
> We should of course keep your test case and if you had time or anyone who
> wants to take it, we could try to make it run on other installers as well.
> We have now an abstraction layer to connect to the deployed nodes
> regardless of the installer, we could probably adapt the code to use it and
> make it “installer agnostic”.  There are also a few things I’d like to
> expect from the test case as Functest has evolved, it would be great that
> the test case adapts to it.
>
>
>
> How will be your availability for Euphrates? If you don’t have much time
> maybe we could propose it as an intern project.
>
>
>
> Regards,
>
> Jose
>
>
>
>
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Luke Hinds
> *Sent:* Monday, April 03, 2017 09:36 AM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] [functest] Security Scanning
>
>
>
> Hi Functest'ers,
>
>
>
> I am aware I have not been as active on security scanning as I originally
> hoped, largely due to being v-busy working on upstream. I have also not
> seen much uptake in contributions from others or any requests for support
> or enhancements to make from operators / users of OPNFV.
>
>
>
> With the above snippet in mind, would you like to revisit the projects use
> in functest? I am not saying I wish to decommission, as I put quite a good
> number of hours into the code, but at the same time I am aware my
> contributions have not been very active and I am not sure if that will
> change in the foreseeable future. You might see otherwise and like to
> enhance it further, so it seems a discussion could be worthwhile.
>
>
>
> If you would like we could have this as a topic on a functest meeting or
> alternately I will be at the plugfest too.
>
>
>
> Cheers,
>
>
>
> Luke
>



-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Trying PROX

[opnfv-tech-discuss] [vsperf] Summit CFP - VSPERF submission

[opnfv-tech-discuss] OpenRetriever Project Meeting

[opnfv-tech-discuss] [opnfv-tech-discussion][availability][doctor]Discussion of HA API with the doctor team

[opnfv-tech-discuss] 答复: [opnfv-tech-discussion][availability]project meeting on Mar. 29

[opnfv-tech-discuss] [mano-wg] OPNFV D 1.0 MANO review and D/E TOSCA for Scenario, API + usecase discussions Meeting #25

[opnfv-tech-discuss] [Update] OPNFV Release Meeting (ASIA) - IRC Only

Re: [opnfv-tech-discuss] [vsperf] Trying PROX

[opnfv-tech-discuss] [vsperf] Trying PROX

[opnfv-tech-discuss] OPNFV Danube Announced Today

Re: [opnfv-tech-discuss] Congress on TryStack?

Re: [opnfv-tech-discuss] [functest] Security Scanning

Re: [opnfv-tech-discuss] [functest] Security Scanning

13 matches

Site Navigation

Mail list logo

Footer information