[opnfv-tech-discuss] Canceled: OPNFV XCI Meeting

[Fatih Degirmenci via Lists.Opnfv.Org]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nWelcome to OPNFV XCI Meeting.\n\nYou can
  see the agenda for the upcoming meetings and add topics you would like to
  discuss directly on it https://etherpad.opnfv.org/p/xci-meetings\n\nMeeti
 ng Logistics:\n* Day/Time: Bi-weekly on Wednesdays at 13:00UTC\n* Zoom: ht
 tps://zoom.us/j/2362828999\n* Zoom dial-in numbers are available on: https
 ://zoom.us/zoomconference\n* IRC: #opnfv-pharos channel on Freenode Networ
 k\n\n/Fatih\n
RRULE:FREQ=WEEKLY;UNTIL=20191218T14Z;INTERVAL=2;BYDAY=WE;WKST=SU
EXDATE;TZID=W. Europe Standard Time:20190925T15
UID:622C8A69-56F9-491E-A9DA-F5F85EAF729F
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV XCI Meeting
DTSTART;TZID=W. Europe Standard Time:20190731T15
DTEND;TZID=W. Europe Standard Time:20190731T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20191107T025947Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:Zoom and IRC
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2117572014
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23711): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23711
Mute This Topic: https://lists.opnfv.org/mt/45040984/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Canceled: OPNFV XCI Meeting

[Fatih Degirmenci via Lists.Opnfv.Org]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:This week’s meeting is cancelled due to ONS. T
 alk to you in 2 weeks.\n\n/Fatih\n\nHi\,\n\nWelcome to OPNFV XCI Meeting.\
 n\nYou can see the agenda for the upcoming meetings and add topics you wou
 ld like to discuss directly on it https://etherpad.opnfv.org/p/xci-meeting
 s\n\nMeeting Logistics:\n* Day/Time: Bi-weekly on Wednesdays at 13:00UTC\n
 * Zoom: https://zoom.us/j/2362828999\n* Zoom dial-in numbers are available
  on: https://zoom.us/zoomconference\n* IRC: #opnfv-pharos channel on Freen
 ode Network\n\n/Fatih\n
UID:622C8A69-56F9-491E-A9DA-F5F85EAF729F
RECURRENCE-ID;TZID=W. Europe Standard Time:20190925T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV XCI Meeting
DTSTART;TZID=W. Europe Standard Time:20190925T15
DTEND;TZID=W. Europe Standard Time:20190925T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20190924T061103Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:Zoom and IRC
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2117572014
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23601): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23601
Mute This Topic: https://lists.opnfv.org/mt/34273420/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] OPNFV XCI Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\n\n\nWelcome to OPNFV XCI Meeting.\n\n\n\
 nYou can see the agenda for the upcoming meetings and add topics you would
  like to discuss directly on it https://etherpad.opnfv.org/p/xci-meetings\
 n\n\n\nMeeting Logistics:\n\n* Day/Time: Bi-weekly on Wednesdays at 13:00U
 TC\n* Zoom: https://zoom.us/j/2362828999\n\n* Zoom dial-in numbers are ava
 ilable on: https://zoom.us/zoomconference\n\n* IRC: #opnfv-pharos channel 
 on Freenode Network\n\n\n\n/Fatih\n
RRULE:FREQ=WEEKLY;UNTIL=20191218T14Z;INTERVAL=2;BYDAY=WE;WKST=SU
UID:622C8A69-56F9-491E-A9DA-F5F85EAF729F
SUMMARY;LANGUAGE=en-US:OPNFV XCI Meeting
DTSTART;TZID=W. Europe Standard Time:20190731T15
DTEND;TZID=W. Europe Standard Time:20190731T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20190718T093450Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:Zoom and IRC
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2117572014
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"Zoom and IRC"\,"LocationAnnotation":
 ""\,"LocationUri":""\,"LocationStreet":""\,"LocationCity":""\,"LocationSta
 te":""\,"LocationCountry":""\,"LocationPostalCode":""\,"LocationFullAddres
 s":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23376): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23376
Mute This Topic: https://lists.opnfv.org/mt/32518118/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] New Project Proposal: XCI

[Fatih Degirmenci]

Hi OPNFV Community and TSC,

In order to contribute to the integration, deployment, and testing efforts
of NFVi platform within OPNFV and across LFN, serve our end-users by
ensuring the developed platform meets their needs fully, and continue the
collaboration with sister communities, we would like to propose a new
project, XCI, for OPNFV community.

You can see the project proposal on OPNFV Wiki.

https://wiki.opnfv.org/display/PROJ/XCI

We appreciate your feedback on the proposal.

We will also ask the discussion on the proposal to be added to agenda for
OPNFV Technical Discussion Meeting on June 3rd.

/Fatih
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23161): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23161
Mute This Topic: https://lists.opnfv.org/mt/31698872/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] XCI-DEPLOYMENT

[Fatih Degirmenci]

Hi,

As noted in the log, deployment from the tip of OSA master (and stable)
branches are not advised as we step versions after we test them in a
controlled manner.
You can still attempt doing that but it might result in strange failures
depending on the state of the upstream.

So my suggestion will be the same.
Please start with a small virtual deployment of the scenario you want to
try and avoid setting OPENSTACK_OSA_VERSION while doing that.

export INSTALLER_TYPE=osa
export DEPLOY_SCENARIO=os-odl-sfc
export XCI_FLAVOR=mini
export XCI_DISTRO=ubuntu
./xci-deploy.sh

I tried deploying it yesterday using the commands above and the deployment
succeeded.
Once you get this basic deployment working on your environment, you can try
ha as XCI_FLAVOR to go another step to see if that works.

For baremetal, you need PDF and IDF files created in advance for your setup
and passed to xci-deploy.sh as arguments.
You can start with mini flavor for baremetal deployment as well and
continue from there.

/Fatih

On Wed, 8 May 2019 at 14:46, NAZAN CENGIZ  wrote:

> Hi,
> We failed XCI deployment when running ./xci-deploy.sh as below; Could you
> please help me?
>
> PLAY RECAP
> **
> compute00 : ok=36 changed=19 unreachable=0 failed=0
> compute01 : ok=36 changed=19 unreachable=0 failed=0
> controller00 : ok=36 changed=19 unreachable=0 failed=0
> controller01 : ok=36 changed=19 unreachable=0 failed=0
> controller02 : ok=36 changed=19 unreachable=0 failed=0
> opnfv : ok=123 changed=80 unreachable=0 failed=0
>
> ---
> Info: VM nodes are provisioned!
> ---
> Info: Deploying 'osa' installer
> ---
>
>
> +++
> WARNING: We have detected that you are trying to OpenStack-Ansible from
> stable or master branch.
> This will likely not work because, unless you know what you are doing, you
> are going
> to be trying something that has not been verified by XCI or upstream fully.
> This is _NOT_ supported in any way but we can try to make it work for you.
> Either way you are on your own so please do not report bugs as they will
> be considered invalid.
>
> +++
>
> ===> Downloading the sources-branch-updater-lib.sh library
> ===> Cloning the openstack-ansible repository
> fatal: unable to connect to git.openstack.org:
> git.openstack.org[0: 23.253.125.17]: errno=Connection timed out
> git.openstack.org[1: 2001:4800:7817:103:be76:4eff:fe04:e3e3]:
> errno=Network is unreachable
>
>
> This e-mail and any attached files are confidential and may be legally
> privileged. If you are not the addressee, any disclosure, reproduction,
> copying, distribution, or other dissemination or use of this communication
> is strictly prohibited. If you have received this transmission in error
> please notify the sender immediately and then delete this mail.
> E-mail transmission cannot be guaranteed to be secure or error free as
> information could be intercepted, corrupted, lost, destroyed, arrive late
> or incomplete, or contain viruses. The sender therefore does not accept
> liability for any errors or omissions in the contents of this message which
> arise as a result of e-mail transmission or changes to transmitted date not
> specifically approved by the sender.
> If this e-mail or attached files contain information which do not relate
> to our professional activity we do not accept liability for such
> information.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23110):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23110
> Mute This Topic: https://lists.opnfv.org/mt/31542752/1177073
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> fde...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23115): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23115
Mute This Topic: https://lists.opnfv.org/mt/31542752/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] XCI DEPLOYMENT

[Fatih Degirmenci]

Hi Nazan,

As Yolanda says, it would be good if you can provide more details with
regards to the problems you are experiencing.

- what distro are you using? (centos/ubuntu/opensuse?)
- what type of deployment you are doing? (virtual/baremetal?)
- which scenario you are trying?

Here are some ideas.

If you are attempting to use Centos then I should say it is not supported
due to upstream issues at the time we were working on supporting it so
please try Ubuntu 16.04 or openSUSE 42.3 if possible.
You can set the distro to use before executing xci-deploy.sh script. Just
set env variable XCI_DISTRO to ubuntu or opensuse.

My suggestion for you to start with virtual deployments as baremetal
deployments require you to have POD and Installer Descriptor Files ready
beforehand. You can see examples in releng-xci repo. [1][2]
For virtual deployments, you don't need them as they are already provided.
You need a machine with 18+ cores and 36GB+ of ram for virtual deployments
for the smallest flavor which is mini.

As a side note, things might be broken as we haven't done a good job to
maintain things lately.

[1] https://github.com/opnfv/releng-xci/blob/master/xci/var/lf-pod4-pdf.yml
[2] https://github.com/opnfv/releng-xci/blob/master/xci/var/lf-pod4-idf.yml

/Fatih

On Mon, 6 May 2019 at 20:47, NAZAN CENGIZ  wrote:

>
>
> --
> *Kimden: *"NAZAN CENGIZ" 
> *Kime: *"yroblamo" 
> *Gönderilenler: *6 Mayıs Pazartesi 2019 15:32:50
> *Konu: *Re: XCI DEPLOYMENT
>
> Hi,
> We starting now XCI deployment on Centos 7 as Jumphost. Could you please
> help me?
>
> But we made fail;
>
>
> --
> *Kimden: *"yroblamo" 
> *Kime: *"NAZAN CENGIZ" 
> *Gönderilenler: *17 Nisan Çarşamba 2019 9:40:32
> *Konu: *Re: XCI DEPLOYMENT
>
> Hi, that's the documentation that we have, sorry. I think it should be
> easy to follow. Can you clarify what are your problems and what parts you
> don't understand?
>
> On Tue, Apr 16, 2019 at 9:46 PM NAZAN CENGIZ 
> wrote:
>
>> Hi,
>>
>> I tried XCI deployment one years month ago. But it installation made
>> failed. Please could you share setup XCI for an sources?
>>
>> I look;
>> https://opnfv-releng-xci.readthedocs.io/en/latest/xci-user-guide.html.
>>
>> But I could't understand on
>> https://opnfv-releng-xci.readthedocs.io/en/latest/xci-user-guide.html.
>>
>> Please could you easy source?
>>
>> Best Regards
>> Nazan
>>
>> This e-mail and any attached files are confidential and may be legally
>> privileged. If you are not the addressee, any disclosure, reproduction,
>> copying, distribution, or other dissemination or use of this communication
>> is strictly prohibited. If you have received this transmission in error
>> please notify the sender immediately and then delete this mail.
>> E-mail transmission cannot be guaranteed to be secure or error free as
>> information could be intercepted, corrupted, lost, destroyed, arrive late
>> or incomplete, or contain viruses. The sender therefore does not accept
>> liability for any errors or omissions in the contents of this message which
>> arise as a result of e-mail transmission or changes to transmitted date not
>> specifically approved by the sender.
>> If this e-mail or attached files contain information which do not relate
>> to our professional activity we do not accept liability for such
>> information.
>>
>>
>
> --
>
> Yolanda Robla Mota
>
> Principal Software Engineer, RHCE
>
> Red Hat
>
> 
>
> C/Avellana 213
>
> Urb Portugal
>
> yrobl...@redhat.comM: +34605641639
> 
> 
>
>
> This e-mail and any attached files are confidential and may be legally
> privileged. If you are not the addressee, any disclosure, reproduction,
> copying, distribution, or other dissemination or use of this communication
> is strictly prohibited. If you have received this transmission in error
> please notify the sender immediately and then delete this mail.
> E-mail transmission cannot be guaranteed to be secure or error free as
> information could be intercepted, corrupted, lost, destroyed, arrive late
> or incomplete, or contain viruses. The sender therefore does not accept
> liability for any errors or omissions in the contents of this message which
> arise as a result of e-mail transmission or changes to transmitted date not
> specifically approved by the sender.
> If this e-mail or attached files contain information which do not relate
> to our professional activity we do not accept liability for such
> information.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#23100):
> https://lists.opnfv.org/g/opnfv-tech-discuss/message/23100
> Mute This Topic: https://lists.opnfv.org/mt/31523281/1177073
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  [
> fde...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [opnfv-tech-discuss] DOVETAIL + XCI , Running the SFC TCs

[Fatih Degirmenci]

Hi Dan,

We are still working on setting the roadmap for XCI and will come back to
you once we have a consensus around how to move forward with XCI.

/Fatih

On Tue, 23 Apr 2019 at 08:49, xudan  wrote:

> Hi XCI team,
>
>
>
> I’d like to invite you to join Dovetail weekly meeting [1] to give some
> introduction and updates about XCI as we discussed several weeks ago. And
> also Panos can give more details about what he has done.
>
> Please let us know when it’s okay for you.
>
>
>
> [1] https://wiki.opnfv.org/display/meetings/Dovetail
>
>
>
> Thanks,
>
> Dan Xu
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org [mailto:
> opnfv-tech-discuss@lists.opnfv.org] *On Behalf Of *Panagiotis Karalis
> *Sent:* Friday, April 19, 2019 11:26 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Cc:* dmcbr...@linuxfoundation.org; fatih.degirme...@est.tech
> *Subject:* [opnfv-tech-discuss] DOVETAIL + XCI , Running the SFC TCs
>
>
>
> Hi all,
>
>
>
> After an initiative, I’ve started with a first attempt to introduce the
> XCI in the dovetail and as I promised to David,
>
> I’ m sending you this email with my progress so far.
>
> Specifically, I tried to deployed the dovetail on XCI installer and run
> TCs through dovetail tool.
>
>
>
> XCI details:
>
> -  OS: Ubuntu (check the rest requirements [1])
>
> -  Flavor: mini (for more details [1])
>
> -  Deploy Scenario: os-odl-sfc-noha and follow the rest
> instructions for SFC deployment with XCI [2]
>
> Waiting until  the XCI deployment is completed.
>
>
>
> After that, the dovetail tool installation takes place following  the
> relevant instructions from UG [3] in OPNFV VM of XCI (ssh
> root@192.168.122.2).
>
>
>
> My first action was to verify that the containers which have been
> downloaded via dovetail project were run properly.
>
> So, using the functest-features:gambia container , I was trying to run
> different test scenarios.
>
> At this point, I noticed that the only scenario that was running properly
> (for my configuration setup and environment) was the SFC test cases.
>
>
>
> After that I tried to run the same scenario through dovetail:
>
> -  I prepared a patch in order to trigger this scenario [4].
>
> -  I prepared the env_config.sh and pod.yaml files according to
> the XCI topology and configuration
>
> -  I added in the ‘env_config.sh’ of dovetail the following
> parameters
>
> o   DEPLOY_SCENARIO=os-odl-sfc-noha
>
> o   INSTALLER_TYPE=osa
>
> o   INSTALLER_IP=192.168.122.2
>
> o   EXTERNAL_NETWORK=ext-net
>
>
>
> The result was partially successfully.
>
> The test scenario has been started and the OS components are created
> successfully (like routes, networks  etc).
>
> At the end, I got an error which seems more or less related to my
> environment.
>
> As far as I remember, I got the same error when I tried to run the SFC
> test case directly through functest-features:gambia
>
>
>
> *Another alternative that I tried after the aforementioned results*
>
>
>
> I used the patch [5] changing the relationship between the SFC test cases
> and the XCI installer.
>
> [This patch makes the SFC TCs independently from each installer, so the
> information like the server’s IP is fetched directly from a yaml file that
> prepared by user or by dovetail (the pod.yaml in our case)]  and not by
> installer.
>
>
>
> Using this patch, I have skipped the step to add the above parameters in
> the environment file (env_config.sh), since this information is retrieved
> directly from pod.yaml which is copied in the container from dovetail.
>
>
>
> *BUT the important thing is that the results are much better.*
>
>
>
> The investigation is in progress! J
>
>
>
> Let me know if there are questions / comments about the above steps or
> results.
>
> Moreover, If someone have time to support / contribute this attempt,
> he/she is more than welcome!
>
>
>
> Have a nice weekend!
>
> BR
>
> Panos
>
>
>
> [1]
> https://opnfv-releng-xci.readthedocs.io/en/latest/xci-user-guide.html#xci-user-guide
>
> [2] https://wiki.opnfv.org/display/sfc/Deploy+OPNFV+SFC+scenarios
>
> [3]
> https://github.com/opnfv/dovetail/blob/master/docs/testing/user/userguide/testing_guide.rst
>
> [4] https://gerrit.opnfv.org/gerrit/#/c/67615/
>
> [5] https://gerrit.opnfv.org/gerrit/#/c/67492/
>
>
>
>
>
>
>
>
> *Panagiotis Karalis *Software Engineer
>
> SDN/NFV Team
> __
> Intracom Telecom
> 19.7 km Markopoulou Ave., Peania, GR 19002
> t:   +30 2106671499
>
> *pkara...@intracom-telecom.com  *www.
> intracom-telecom.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *JOIN US*
>
> MWC Shanghai
>
> 26-28 June
> Shanghai, China
>
>
>
> GITEX Technology Week
>
> 6-10 October
>
> Dubai, UAE
>
>
>
> MWC Los Angeles
>
> 22-24 October
>
> Los Angeles, USA
>
>
>
> Futurecom
>
> 28-31 October
> Sao Paulo, Brazil
>
>
>
> AfricaCom
>
> 12-14 November
> Cape Town, South Africa
>
>
>
> MWC Barcelona
>
> 24-27 February 2020
>
> Barcelona, Spain
>
>
>
> The 

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nWelcome to OPNFV Cross Community CI (XCI
 ) Meeting!\n\nPlease note that XCI meetings will be held on a bi-weekly ba
 sis during summer. The meeting dates are 2018-07-11\, 2018-07-25 (chaired 
 by Manuel Buil)\, and 2018-08-08.\n\nWe will have OpenCI as standing agend
 a item to provide updates to XCI Team and interested OPNFV community membe
 rs.\nAll OPNFV community members who want to learn more about OpenCI Initi
 ative\, wish to keep themselves up to date with the latest developments an
 d thinking of contributing is welcome to join to XCI meeting.\n\nYou can s
 ee the agenda for the upcoming meeting and the links to the minutes of the
  previous meetings on https://etherpad.opnfv.org/p/xci-meetings\n\nPlease 
 note that this is an IRC-only meeting on #opnfv-pharos channel on freenode
 \, held on a weekly basis.\nPlease let me know in case if you want to have
  meeting with voice/screen sharing to discuss/demo things in advance so we
  can fix GTM for that meeting.\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org
 /pages/viewpage.action?pageId=8687635\nXCI @ OPNFV Jenkins: https://build.
 opnfv.org/ci/view/OPNFV%20XCI/\nOpenCI Wiki: https://gitlab.openci.io/open
 ci/community/wikis/home\n\n/Fatih\n\n
UID:4D0631BF-C20D-4B7B-9A6F-D9FA6208829B
RECURRENCE-ID;TZID=W. Europe Standard Time:20181128T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20181128T15
DTEND;TZID=W. Europe Standard Time:20181128T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20181128T120428Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2116628331
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22464): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22464
Mute This Topic: https://lists.opnfv.org/mt/28431341/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nThis week’s meeting is cancelled due t
 o OpenStack Summit.\nTalk to you next time!\n\n/Fatih\n\n\n\nWelcome to OP
 NFV Cross Community CI (XCI) Meeting!\n\nPlease note that XCI meetings wil
 l be held on a bi-weekly basis during summer. The meeting dates are 2018-0
 7-11\, 2018-07-25 (chaired by Manuel Buil)\, and 2018-08-08.\n\nWe will ha
 ve OpenCI as standing agenda item to provide updates to XCI Team and inter
 ested OPNFV community members.\nAll OPNFV community members who want to le
 arn more about OpenCI Initiative\, wish to keep themselves up to date with
  the latest developments and thinking of contributing is welcome to join t
 o XCI meeting.\n\nYou can see the agenda for the upcoming meeting and the 
 links to the minutes of the previous meetings on https://etherpad.opnfv.or
 g/p/xci-meetings\n\nPlease note that this is an IRC-only meeting on #opnfv
 -pharos channel on freenode\, held on a weekly basis.\nPlease let me know 
 in case if you want to have meeting with voice/screen sharing to discuss/d
 emo things in advance so we can fix GTM for that meeting.\n\nXCI @ OPNFV W
 iki: https://wiki.opnfv.org/pages/viewpage.action?pageId=8687635\nXCI @ OP
 NFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/\nOpenCI Wiki: ht
 tps://gitlab.openci.io/openci/community/wikis/home\n\n/Fatih\n\n
UID:4D0631BF-C20D-4B7B-9A6F-D9FA6208829B
RECURRENCE-ID;TZID=W. Europe Standard Time:20181114T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20181114T15
DTEND;TZID=W. Europe Standard Time:20181114T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20181112T113033Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2116628331
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22364): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22364
Mute This Topic: https://lists.opnfv.org/mt/28114372/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [opnfv-tsc] Results of OPNFV TSC Election #election #announce

[Fatih Degirmenci]

Congratulations to all new and returning members of the TSC.

/Fatih

On 26 September 2018 at 12:10, David McBride
 wrote:
> Team,
>
> I'm pleased to announce the results of the TSC election.
>
> Bin Hu
> Cedric Ollivier
> Cristina Pauna
> Emma Foley
> Frank Brockners
> Georg Kunz
> Manuel Buil
> Mark Beierl
> Qiao Fu
> Rex Lee
> Tim Irnich
> Tim Rozet
> Trevor Bramwell
> Trevor Cooper
> Yang (Gabriel) Yu
>
> The new TSC members will assume their roles as soon as the TSC chair
> election is completed near the end of October.
>
> Election Stats:
>
> 23 nominees
> 216 eligible voters
> 107 votes cast (slightly less than 50% of eligible voters)
>
> Thanks to all of the nominators and nominees, as well as those who cast
> votes.
>
> Let me know if you have any questions.
>
> David
>
>
> --
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> _._,_._,_
> 
> Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#4681) | Reply To Sender | Reply To Group | Mute This
> Topic | New Topic
> Mute #election | Mute #announce
> Your Subscription | Contact Group Owner | Unsubscribe [fde...@gmail.com]
>
> _._,_._,_
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22097): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22097
Mute This Topic: https://lists.opnfv.org/mt/26231007/21656
Mute #election: https://lists.opnfv.org/mk?hashtag=election=2783016
Mute #announce: https://lists.opnfv.org/mk?hashtag=announce=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] [yardstick][xci] Yardstick Test Suites for Kubernetes Scenarios

[Fatih Degirmenci]

Hi,

We have few k8s scenarios using different networking plugins and another one 
with istio and we are in the process to enable Yardstick to test these. [1]

While looking at the available k8s test suites in Yardstick repo, we weren’t so 
sure which one to use for the k8s scenarios other than k8-nosdn-nofeature. [2]

Can you please advise us regarding what to do in this case?

Ps. We currently set all scenarios to be tested using the suite for 
k8-nosdn-nofeature-noha scenario.

[1] 
https://gerrit.opnfv.org/gerrit/gitweb?p=releng-xci.git;a=blob;f=xci/opnfv-scenario-requirements.yml
[2] 
https://gerrit.opnfv.org/gerrit/gitweb?p=yardstick.git;a=tree;f=tests/opnfv/test_suites

/Fatih

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21942): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21942
Mute This Topic: https://lists.opnfv.org/mt/25210532/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nPlease note that XCI meetings will be held on a bi-w
 eekly basis during summer. The meeting dates are 2018-07-11\, 2018-07-25 (
 chaired by Manuel Buil)\, and 2018-08-08.\n\n\n\nWe will have OpenCI as st
 anding agenda item to provide updates to XCI Team and interested OPNFV com
 munity members.\n\nAll OPNFV community members who want to learn more abou
 t OpenCI Initiative\, wish to keep themselves up to date with the latest d
 evelopments and thinking of contributing is welcome to join to XCI meeting
 .\n\n\n\nYou can see the agenda for the upcoming meeting and the links to 
 the minutes of the previous meetings on https://etherpad.opnfv.org/p/xci-m
 eetings\n\n\n\nPlease note that this is an IRC-only meeting on #opnfv-phar
 os channel on freenode\, held on a weekly basis.\n\nPlease let me know in 
 case if you want to have meeting with voice/screen sharing to discuss/demo
  things in advance so we can fix GTM for that meeting.\n\n\n\nXCI @ OPNFV 
 Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId=8687635\n\nXCI @
  OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/\n\nOpenCI Wik
 i: https://gitlab.openci.io/openci/community/wikis/home\n\n\n\n/Fatih\n\n\
 n
RRULE:FREQ=WEEKLY;COUNT=7;INTERVAL=2;BYDAY=WE;WKST=SU
UID:4D0631BF-C20D-4B7B-9A6F-D9FA6208829B
SUMMARY;LANGUAGE=en-US:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180919T15
DTEND;TZID=W. Europe Standard Time:20180919T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180905T115710Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116628331
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"IRC-only (#opnfv-pharos on freenode)
 "\,"LocationAnnotation":""\,"LocationUri":""\,"LocationStreet":""\,"Locati
 onCity":""\,"LocationState":""\,"LocationCountry":""\,"LocationPostalCode"
 :""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce][election] Opening nominations for OPNFV Technical Steering Committee (TSC)

[Fatih Degirmenci]

Thanks a lot Alec for the nomination.

There are very good candidates with new perspectives, fresh ideas and different 
experiences.
I believe they will make great contributions to the TSC, OPNFV community and 
the communities we are collaborating with.

I want to continue focusing on CD in open source and cross community 
collaboration so I decline the nomination.

/Fatih
From: "opnfv-...@lists.opnfv.org"  on behalf of 
David McBride 
Date: Tuesday, 4 September 2018 at 19:35
To: "Alec Hothan (ahothan)" 
Cc: "opnfv-...@lists.opnfv.org" , 
"opnfv-tech-discuss@lists.opnfv.org" , 
Heather Kirksey , Fatih Degirmenci 
, Trevor Cooper 
Subject: Re: [opnfv-tsc] [announce][election] Opening nominations for OPNFV 
Technical Steering Committee (TSC)

Fatih - do you accept the nomination?

On Tue, Sep 4, 2018 at 9:01 AM Alec Hothan (ahothan) 
mailto:ahot...@cisco.com>> wrote:
I would like to nominate Trevor Cooper (Intel) and Fatih Degirmenci (Ericsson) 
to the TSC.

Both Trevor and Fatih have shown excellent interaction across projects and 
expertise in testing and release management. I am confident they will provide 
the best guidance to the TSC.

Thank You

  Alec


From: mailto:opnfv-...@lists.opnfv.org>> on behalf 
of David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Date: Friday, August 31, 2018 at 9:56 AM
To: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>, 
TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: "tim.irn...@ericsson.com<mailto:tim.irn...@ericsson.com>" 
mailto:tim.irn...@ericsson.com>>, Heather Kirksey 
mailto:hkirk...@linuxfoundation.org>>
Subject: Re: [opnfv-tsc] [announce][election] Opening nominations for OPNFV 
Technical Steering Committee (TSC)

Team,

We've reached the halfway point for the nomination period.  Nominations will 
close in 1 week, on Sept 7 at 5 p.m. (PT).  So far, we have only 5 nominations. 
 Keep in mind that we need to elect 15 people to the TSC, so keep those 
nominations coming!

David

On Wed, Aug 29, 2018 at 8:47 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

I'm surprised that nominations have been open for 5 days and I've yet to see a 
single nomination.  Someone needs to break the ice and get this started.  
Nominations close Sept 7.  Thanks.

David

On Fri, Aug 24, 2018 at 10:47 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

Today, we begin nominations for a new TSC, consisting of 15 members, in 
accordance with the Community Election 
Procedures<https://wiki.opnfv.org/display/DEV/Community+Election+Procedure>.  
Individuals who are eligible to both vote and run for a TSC position are those 
with 20 or more contributions on this list of active 
contributors<https://wiki.opnfv.org/display/DEV/2018+Consolidated+Contributions>.
  Before nominating someone, please consult the list and verify that the 
individual has 20 or more contributions.  You may find a schedule of election 
activities 
here<https://wiki.opnfv.org/display/DEV/2018+TSC+and+TSC+Chair+Election+Schedule+of+Activities>.

PTL Input to the Active Contributor List
Note that the election procedures have a provision for adding and individual to 
the active contributor list, who has less than 20 contributions, yet who has 
make significant contributions to the OPNFV community.  Per the election 
procedure:

PTLs have an input on the "active contributor list" compiled over a 2-week 
review period (with a view that this step primarily targets at making sure 
qualified people that haven't been identified via the metric get added to the 
list)
I am working with the TSC to define a specific process for this situation.  In 
the mean time, if you are a PTL, and you would like to add someone to the 
active contributor list, please contact me directly with the name and a brief 
statement about why they should be included on the list.  Note that this action 
simply adds them to the active contributor list, they still must be nominated, 
separately.  Also, note that the 2-week review period for the active 
contributor list, cited in the election procedure, ends on Aug 31.

Nomination procedure
1.   You may nominate yourself, or someone else.
oRemember that both you and the person nominated must be on the active 
contributor 
list<https://wiki.opnfv.org/display/DEV/2018+Consolidated+Contributions> with 
20 or more contributions.
oIf you nominate someone else, I will confirm with that person that they 
accept the nomination.
2.   Announce the nomination with a "reply all" to this email prior to 5 
p.m. (PT), Sept 7.
3.   Please include the following information:
oName of the nominee
oThe nominee's organization
oA brief statement about the nominees qualifications and contributions to 
the OPNFV community.
4.   Nominations close at 5 p.m. (PT) on Sept 7.  See the entire 

[opnfv-tech-discuss] [xci] Updates on CI Evolution, Dynamic CI, OpenStack Rocky, k8s, MANO, and more

[Fatih Degirmenci]

Hi,

It’s been quite some time we provided an update regarding XCI to the OPNFV 
community so here it is.

Infra/CICD Improvements/Implementations:

  *   CI Evolution:
 *   We are activating different phases in XCI pipelines. Currently verify, 
post-merge, and daily are activated.
 *   We are gradually increasing the bar for promotion and will be 
activating Functest Smoke and Yardstick on different phases.
  *   Scenarios owned by projects:
 *   Scenarios are developed in project repos who own them and they get 
plugged into XCI.
 *   When a patch comes in to the project repo where the scenario is 
located, XCI starts the deployment and testing of that scenario and provides 
feedback directly on the patch.
  *   Ability to Override Versions:
 *   Projects have ability to override versions of upstream components 
depending on their needs.
 *   This makes it possible for projects to use different versions than 
what’s set within XCI by default. (XCI is constantly bumping to later versions)
  *   Full Isolation from Host:
 *   XCI leaves nearly nothing XCI-specific on the host system and all the 
deployment and test activities are driven from a VM located on jumphost.
 *   This enables reproducibility and predictability of CI and also limits 
the potential issues that could be caused due to the leftovers on hosts systems.
 *   Sandbox users will benefit from this greatly since their machines will 
not be heavily impacted by the use of the sandbox so they can use the same 
machine for other purposes.
  *   Being Agnostic to host OS:
 *   Thanks to the isolation summarized above, the OS of the jumphost 
doesn’t matter since the user can decide what OS to provision the target nodes 
with a single environment variable.
  *   PDF, IDF:
 *   PDF and IDF are natively supported.
  *   Dynamic CI:
 *   With the help of PDF, IDF, isolation from host and being OS agnostic, 
XCI will be ready to demonstrate the concepts of dynamic CI when the baremetal 
work is concluded.
  *   Baremetal:
 *   Baremetal work is full in progress and it will be available soon.

Versions:

  *   OpenStack:
 *   Rocky
 *   XCI brought in OpenStack Rocky same day as OpenStack released Rocky.
  *   OpenDaylight:
 *   Oxygen
 *   Will move to Fluorine soon.
  *   Kubernetes:
 *   v1.10.4
 *   Will gradually move to the tip of master in collaboration with CNCF 
Cross Cloud CI Team.
  *   OSM:
 *   v4.0.1
 *   Collaboration with OSM community has started to move to latest on 
master.
  *   ONAP:
 *   Initial integration using Beijing in collaboration with Orange by 
reusing/adapting Ansible role is in progress.
 *   Will move to Casablanca and then to master once the initial 
integration is concluded.

Scenario/Feature Support:

  *   OpenStack:
 *   Integrated: os-nosdn-nofeature, os-odl-nofeature, os-odl-sfc, 
os-odl-bgpvpn, os-nosdn-osm
 *   WIP: os-odl-sfc_osm
 *   TBD: os-nosdn-vmha, blazar, congress
  *   K8S:
 *   Integrated: k8-calico-nofeature, k8-canal-nofeature, 
k8-contiv-nofeature, k8-flannel-nofeature, k8-nosdn-istio, k8-nosdn-nofeature
 *   WIP: k8-calico-onap

/Fatih

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#21905): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21905
Mute This Topic: https://lists.opnfv.org/mt/25138111/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [XCI]: timeout reached while inspecting the node

[Fatih Degirmenci]

Hi Mohamad,

We had some issues due to upstream and they are resolved now.

Can you give another try using the tip of releng-xci as of today. (sha: 
973920421d98159a3d91790859061ee718cd1e07)
You will get OpenStack Rocky RC1.

You can reach out to us on freenode #opnfv-pharos channel so we can help you 
with troubleshooting if it happens with the version I suggested above.

/Fatih

From: "opnfv-tech-discuss@lists.opnfv.org"  
on behalf of "ha...@eantc.de" 
Date: Wednesday, 15 August 2018 at 16:54
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [XCI]: timeout reached while inspecting the node

Hi all,

I was trying to deploy Opnfv  via sandbox on a vm and after an hour of 
installation, I got the following error. Any idea what might have caused this 
error?
TASK [ironic-inspect-node : Execute node introspection - noauth_mode] 

^[[D0fatal: [controller00 -> 192.168.122.2]: FAILED! => {"changed": false, 
"failed": true, "msg": "Inspection of node e1369efa-5391-5035-8533-3a065c44a584 
failed, last error: timeout reached while inspecting the node"}
fatal: [compute00 -> 192.168.122.2]: FAILED! => {"changed": false, "failed": 
true, "msg": "Timeout waiting for node transition to target state of 'inspect'"}
to retry, use: --limit 
@/home/releng-xci/xci/infra/bifrost/playbooks/opnfv-virtual.retry

PLAY RECAP 
***
compute00  : ok=7changed=1unreachable=0failed=1
controller00   : ok=7changed=1unreachable=0failed=1
opnfv  : ok=121  changed=78   unreachable=0failed=0


-
Oh no! The XCI deployment failed miserably :-(

If you need help, please choose one of the following options
* #opnfv-pharos @ freenode network
* opnfv-tech-discuss mailing list 
(https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss)
  - Please prefix the subject with [XCI]
* https://jira.opnfv.org (Release Engineering project)

Do not forget to submit the following information on your bug report:

releng-xci tree status: clean
opnfv/releng-xci version: 45c9deef6b77df5d77e37ac2b8f71f03cc0ac7a3
openstack/bifrost version: 81e48e7b488c15516503b2b08f087f4a7ae9a673
openstack/openstack-ansible version: 5dbc4c5b67e67c370b04099c7dce56dd2f559288
xci flavor: mini
xci installer: osa
xci scenario: os-nosdn-nofeature
Environment variables:
ANSIBLE_ROLES_PATH=/home/opnfv/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/releng-xci/xci/playbooks/roles:/home/releng-xci/.cache/repos/bifrost/playbooks/roles
XCI_LIB_SOURCED=1
DEPLOY_SCENARIO=os-nosdn-nofeature
XCI_PATH=/home/releng-xci
XCI_FLAVOR=mini
ANSIBLE_HOST_KEY_CHECKING=False
INSTALLER_TYPE=osa
XCI_CEPH_ENABLED=false
OPENSTACK_REQUIREMENTS_VERSION=207ac2e166f0874b7ff891535bdb78ecf36cabc6
XCI_SCENARIOS_CACHE=/home/releng-xci/.cache/repos/scenarios
OPENSTACK_OSA_VERSION=5dbc4c5b67e67c370b04099c7dce56dd2f559288
OPENSTACK_OSA_GIT_URL=https://git.openstack.org/openstack/openstack-ansible
ANSIBLE_CALLBACK_PLUGINS=/etc/ansible/roles/plugins/callback:/home/releng-xci/venv/local/lib/python2.7/site-packages/ara/plugins/callbacks
CORE_OPENSTACK_INSTALL=false
ANSIBLE_LIBRARY=/home/opnfv/.ansible/plugins/modules:/usr/share/ansible/plugins/modules:/home/releng-xci/.cache/repos/bifrost/playbooks/library
XCI_PLAYBOOKS=/home/releng-xci/xci/playbooks
OPNFV_FUNCTEST_HEALTHCHECK_DOCKER_IMAGE_DIGEST=sha256:faa1ec5778ac1580cc46f0e4f5abec24026868b95fc6fc3ae6023275dc980c2d
XCI_SSL_SUBJECT=/C=US/ST=California/L=San Francisco/O=IT/CN=xci.releng.opnfv.org
XCI_ANSIBLE_PIP_VERSION=2.4.4.0
XCI_DISTRO=ubuntu
OPENSTACK_OSA_OPENRC_GIT_URL=https://git.openstack.org/openstack/openstack-ansible-openstack_openrc
OPNFV_RELENG_VERSION=master
OPENSTACK_OSA_HAPROXY_GIT_URL=https://git.openstack.org/openstack/openstack-ansible-haproxy_server
OPENSTACK_OSA_ETC_PATH=/etc/openstack_deploy
OPNFV_HOST_IP=192.168.122.2
OPNFV_RELENG_GIT_URL=https://gerrit.opnfv.org/gerrit/releng-xci.git
OPENSTACK_BIFROST_GIT_URL=https://git.openstack.org/openstack/bifrost
OPNFV_XCI_CACHE=/root/releng-xci/.cache
XCI_KUBE_ANSIBLE_PIP_VERSION=2.4.4
XCI_ANSIBLE_PARAMS= -e xci_path=/home/releng-xci
XCI_CACHE=/home/releng-xci/.cache
OPENSTACK_BIFROST_VERSION=81e48e7b488c15516503b2b08f087f4a7ae9a673
OPENSTACK_OSA_PATH=/root/releng-xci/.cache/repos/openstack-ansible
XCI_VENV=/home/releng-xci/venv/
XCI_FLAVOR_ANSIBLE_FILE_PATH=/home/releng-xci/xci/installer/osa/files/mini
-

Best regards
Mohamad


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online 

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nPlease note that XCI meetings will be held on a bi-w
 eekly basis during summer. The meeting dates are 2018-07-11\, 2018-07-25 (
 chaired by Manuel Buil)\, and 2018-08-08.\n\n\n\nWe will have OpenCI as st
 anding agenda item to provide updates to XCI Team and interested OPNFV com
 munity members.\n\nAll OPNFV community members who want to learn more abou
 t OpenCI Initiative\, wish to keep themselves up to date with the latest d
 evelopments and thinking of contributing is welcome to join to XCI meeting
 .\n\n\n\nYou can see the agenda for the upcoming meeting and the links to 
 the minutes of the previous meetings on https://etherpad.opnfv.org/p/xci-m
 eetings\n\n\n\nPlease note that this is an IRC-only meeting on #opnfv-phar
 os channel on freenode\, held on a weekly basis.\n\nPlease let me know in 
 case if you want to have meeting with voice/screen sharing to discuss/demo
  things in advance so we can fix GTM for that meeting.\n\n\n\nXCI @ OPNFV 
 Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId=8687635\n\nXCI @
  OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/\n\nOpenCI Wik
 i: https://gitlab.openci.io/openci/community/wikis/home\n\n\n\n/Fatih\n\n\
 n\n\n
RRULE:FREQ=WEEKLY;COUNT=3;INTERVAL=2;BYDAY=WE;WKST=SU
UID:DA045D7D-6039-454C-AF28-16CA8A407291
SUMMARY;LANGUAGE=en-US:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180711T15
DTEND;TZID=W. Europe Standard Time:20180711T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180626T063616Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116474244
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"IRC-only (#opnfv-pharos on freenode)
 "\,"LocationAnnotation":""\,"LocationUri":""\,"LocationStreet":""\,"Locati
 onCity":""\,"LocationState":""\,"LocationCountry":""\,"LocationPostalCode"
 :""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nCancelling the meeting due to OPNFV Hack
 fest.\n\n/Fatih\n\nHi\,\n\nWelcome to OPNFV Cross Community CI (XCI) Meeti
 ng!\n\nWe will have OpenCI as standing agenda item to provide updates to X
 CI Team and interested OPNFV community members.\nAll OPNFV community membe
 rs who want to learn more about OpenCI Initiative\, wish to keep themselve
 s up to date with the latest developments and thinking of contributing is 
 welcome to join to XCI meeting.\n\nYou can see the agenda for the upcoming
  meeting and the links to the minutes of the previous meetings on https://
 etherpad.opnfv.org/p/xci-meetings\n\nPlease note that this is an IRC-only 
 meeting on #opnfv-pharos channel on freenode\, held on a weekly basis.\nPl
 ease let me know in case if you want to have meeting with voice/screen sha
 ring to discuss/demo things in advance so we can fix GTM for that meeting.
 \n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId=
 8687635\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/
 \nOpenCI Wiki: https://gitlab.openci.io/openci/community/wikis/home\n\n/Fa
 tih\n\n
UID:96BA0653-C9AC-477B-8852-7B62BFFE0894
RECURRENCE-ID;TZID=W. Europe Standard Time:20180606T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180606T15
DTEND;TZID=W. Europe Standard Time:20180606T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180606T073753Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2116299336
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] [releng] New PTL approved

[Fatih Degirmenci]

Hi all,

Trevor Bramwell has been elected as the new PTL for OPNFV Releng with the votes 
from majority of the committers.
Please see the change on Gerrit.

https://gerrit.opnfv.org/gerrit/#/c/57137/

Congratulations Trevor!

/Fatih
 

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

[opnfv-tech-discuss] [releng] Stepping down as Releng PTL

[Fatih Degirmenci]

Hi,

I would like to announce that I decided to step down as Releng PTL.

As you know, I’ve been Releng PTL for quite some time and I believe it is now 
time to let someone else to take this role and bring in new ideas to make 
Releng even better.
I would like to take this opportunity to thank each and every one of you for 
your support and patience to my endless complaints over the years. I think 
we’ve achieved lots of great things together.

With this mail, I would also like to kick off the nomination period for the new 
PTL. If anyone is interested in taking this role, please announce your 
nomination by replying to this mail.
The nomination period will be open until Wednesday, May 9th, 15:00UTC, followed 
by a vote on Gerrit.

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

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nWelcome to OPNFV Cross Community CI (XCI
 ) Meeting!\n\nWe will have OpenCI as standing agenda item to provide updat
 es to XCI Team and interested OPNFV community members.\nAll OPNFV communit
 y members who want to learn more about OpenCI Initiative\, wish to keep th
 emselves up to date with the latest developments and thinking of contribut
 ing is welcome to join to XCI meeting.\n\nYou can see the agenda for the u
 pcoming meeting and the links to the minutes of the previous meetings on h
 ttps://etherpad.opnfv.org/p/xci-meetings\n\nPlease note that this is an IR
 C-only meeting on #opnfv-pharos channel on freenode\, held on a weekly bas
 is.\nPlease let me know in case if you want to have meeting with voice/scr
 een sharing to discuss/demo things in advance so we can fix GTM for that m
 eeting.\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?
 pageId=8687635\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV
 %20XCI/\nOpenCI Wiki: https://gitlab.openci.io/openci/community/wikis/home
 \n\n/Fatih\n\n
UID:96BA0653-C9AC-477B-8852-7B62BFFE0894
RECURRENCE-ID;TZID=W. Europe Standard Time:20180502T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180502T15
DTEND;TZID=W. Europe Standard Time:20180502T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180501T150541Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2116299336
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [barometer]

[Fatih Degirmenci]

Hi,

I’ll only comment on this claim regarding XCI; ”Healtcheck is selected as 
release criteria and as verify step in the new models.”

As highlighted in the commit message of that change and as reiterated in 
response to the comment put by Cedric, the purpose of that change was to 
capture the state of things with XCI at that point in time. New changes are up 
for collecting feedback from the wider community in order to identify criterias 
for the entire pipeline.

https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2018-April/020991.html

/Fatih

/Fatih

On 22 Apr 2018, at 20:17, ollivier.ced...@gmail.com wrote:

Hello Alec,

I fully agree with you. Yes Functest team would have to work on 3 branches (and 
it's not only about cherry-picks):
- stable/fraser (bugfixes)
- stable/gambia (dev)
- master (dev)

It may be possible only if
- Functest team accepts the additionnal work,
- OPNFV implements a new CI/CD job design for Test Frameworks (we can't wait 
for weeks if we have to maintain 3 stable branches)
- we fully redefine our objectives (removing dependencies and splitting our 
repos would become the first steps but it seems much more relevant to verify 
operating VIM),

From the time being, we can ony support the traditionnal track as all technical 
difficulties are unmet.
Please find below my answers to David and TSC about G:

Cédric

I said that Functest is forced to follow both tracks else the new OPNFV models 
can hardly be successful (it may work if OpenStack doesn't introduce big 
changes but who knows at the beginning of th new OpenStack release?).
The "master" model is built from a falsy upward compatibility as we have 
already discussed during your release meetings.
We shouldn't verify scenarios following VIM master by older VIM clients 
(Gambia) even if it could work by exceptions.
Could I please get the latest results of Functest vs XCI?

I'm still thinking about all technical impacts in Functest and OPNFV Features 
testcases:
- requirements synchronization (master could be equal to VIM master or not 
depending on the OPNFV Features)
- dependencies (at least we would have to rewrite our Healthcheck testcases due 
to the dependency to snaps)
- duplicated work (everything has to be cherry-picked or we do skip OpenStack 
Queen)
- possible testcase exclusions (our vnf testcases depend on middlewares such as 
orchestrators which couldn't support master)
- etc.

And we can't support 2 stable branches with the current daily job design:
- no control loop
- wait for days and weeks the results (it will be worse as stable scenarios 
will run in weekly job)

If I must answer right now, we will ony support the traditionnal track.
(And we won't hack Functest to verify a nested master installer (i.e. to bypass 
timeout issues) or to solve possible API version incompatibilities)
Lots of key challenges have already been listed and from the time being only 
Healtcheck is selected as release criteria and as verify step in the new models.
https://wiki.opnfv.org/display/SWREL/User+stories+for+OPNFV+release+artifacts
http://testresults.opnfv.org/functest/gambiachallenges/
https://gerrit.opnfv.org/gerrit/#/c/55951/

Tim (Rozet) and Tim (Irnich) have already proposed their helps regarding 
Functional Gating which is a good start for tracking both.
http://testresults.opnfv.org/functest/gates/

My concern about CI/CD optimizations (stable scenarios will run once a week) is 
opened whatever the tracks supported.

> On dim., 2018-04-22 at 15:43 +, Alec Hothan (ahothan) wrote:
> [sorry sent previous email too early]
>  
> Traditional OpenStack  testing tool have had  a pretty hard time to support 
> multiple openstack releases because the openstack API community has been very 
> opinionated in managing API evolution and backward compatibility.
> I’d like to provide some feedback from my perspective, if you forget for a 
> moment how functest is designed today and testing tools that must run in 
> functest in order to run at all…
>  
> It is still possible for openstack apps in general to support multiple 
> openstack releases but that requires constant adjustment and potentially 
> supporting multiple branches in the worst cases. Whether a project can manage 
> to evade multiple branches depends on its footprint to openstack APIs and 
> some luck.
> A simple example is the openstack api to manage floating IPs was removed 
> starting from python neutron client 10.0.0, following a few releases of 
> deprecation status, of course that broke a lot of apps but luckily there was 
> an easy temporary fix to it: restrict the dependencies to use a version of 
> that API < 10.0.0 and it was luckily working again. The better solution would 
> be to change the code to use the new API for managing floating IPs but that 
> is not an easy path because such API may not even exist or be properly 
> documented (the case of floating IP being pulled without proper replacement 
> API with proper documentation is just one example of 

[opnfv-tech-discuss] [xci] Setting the criterias for basic and feature/scenario specific testing

[Fatih Degirmenci]

Hi,

You either started working with XCI already or expressed interest in 
participating to it so I would like to ask each project to share their opinion 
when it comes to basic and feature/scenario specific testing in order to start 
bringing them into CI used by XCI.
Testing community and release management are also expected to take part in this 
exercise in order to have community-wide understanding and consensus around the 
criterias XCI will be employing.

Please take a look at this change and either add inline comments or directly 
amend the change as you see fit.

https://gerrit.opnfv.org/gerrit/#/c/56135/

The terminology, CI Loops, and Confidence Levels are documented on earlier 
changes the above change depends on and you are more than welcome to review 
them as well.

https://gerrit.opnfv.org/gerrit/#/q/topic:set-promotion-criterias+status:open

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

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nWe will have OpenCI as standing agenda item to provi
 de updates to XCI Team and interested OPNFV community members.\n\nAll OPNF
 V community members who want to learn more about OpenCI Initiative\, wish 
 to keep themselves up to date with the latest developments and thinking of
  contributing is welcome to join to XCI meeting.\n\n\n\nYou can see the ag
 enda for the upcoming meeting and the links to the minutes of the previous
  meetings on https://etherpad.opnfv.org/p/xci-meetings\n\n\n\nPlease note 
 that this is an IRC-only meeting on #opnfv-pharos channel on freenode\, he
 ld on a weekly basis.\n\nPlease let me know in case if you want to have me
 eting with voice/screen sharing to discuss/demo things in advance so we ca
 n fix GTM for that meeting.\n\n\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.or
 g/pages/viewpage.action?pageId=8687635\n\nXCI @ OPNFV Jenkins: https://bui
 ld.opnfv.org/ci/view/OPNFV%20XCI/\n\nOpenCI Wiki: https://gitlab.openci.io
 /openci/community/wikis/home\n\n\n\n/Fatih\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180620T13Z;INTERVAL=1;BYDAY=WE;WKST=SU
UID:96BA0653-C9AC-477B-8852-7B62BFFE0894
SUMMARY;LANGUAGE=en-US:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180411T15
DTEND;TZID=W. Europe Standard Time:20180411T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180405T133154Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116299336
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"IRC-only (#opnfv-pharos on freenode)
 "\,"LocationAnnotation":""\,"LocationUri":""\,"LocationStreet":""\,"Locati
 onCity":""\,"LocationState":""\,"LocationCountry":""\,"LocationPostalCode"
 :""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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] OpenCI is here

[Fatih Degirmenci]

Hi,

I would like to give everyone a short recap of the Cross Community CI/CD and 
Infra workshop that was held on March 24-25 2018 in LA prior to ONS.

30+ participants from 8 different communities/organizations attended to the 
workshop. [1][2]

  *   OPNFV
  *   OpenStack
  *   OpenDaylight
  *   fd.io
  *   CNCF
  *   ONAP
  *   Ansible
  *   LF

Some of the the participants of the workshop develop, operate, and maintain the 
CI/CD and Infra used by the corresponding communities such as

  *   OPNFV Infra/XCI
  *   CNCF Cross Cloud CI
  *   OpenStack Infra/Zuul/OpenLab
  *   LF Releng/Infra

The workshop was a success.

We had 2 full days of intensive and fruitful conversations around different 
topics such as use cases, concerns, constraints, vocabulary, integrating CIs, 
security, testing, tooling, developer feedback and many other related things in 
CI/CD and Infra area.

The conclusion of the workshop is to continue pushing things together by start 
working on several key/initial themes in a collaborative manner and 
invite/involve everyone/communities who is interested in CI/CD and Infra to 
join to this initiative.

I would like to invite and urge OPNFV Community to take part in this because we 
as community faced many of the similar challenges since the very early days of 
OPNFV.
We can tell our story, share our experiences, learn from others and 
collaboratively address the issues in CI/CD and Infra open source ecosystem 
faces.

Please keep an eye on OpenCI Website, https://openci.io, where we will be 
publishing the outcome of the workshop and making announcements.
You can also take a look at the Wiki and start collaborating using the tools we 
have listed there. [3]
There is also an IRC channel #openci on Freenode. Please join to that as well.

Next OpenCI workshops will be held during OpenDev 2018 which is colocated with 
OpenStack Summit Vancouver on May 22-23. I hope and I wish you can join us 
there. [4]

Finally, I would like to thank members of the OPNFV and 7 other communities who 
took part in this workshop.

As I said many times before, what we have now is just the beginning and we are 
on our way to change things.

[1] 
https://wiki.opnfv.org/download/attachments/8687635/XCI_Workshop_March_24_25.pptx?api=v2
[2] 
https://docs.google.com/spreadsheets/d/1enIRDPyAqo2ZgmErge7eOt28LvIWW4hKRH2KkjAIvSI/edit?usp=sharing
[3] https://gitlab.openci.io/openci/community/wikis/home
[4] http://2018.opendevconf.com/

/Fatih


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

[opnfv-tech-discuss] [xci] Committer Promotions for releng-xci

[Fatih Degirmenci]

Hi,

I would like to inform the TSC that Tianwei, Manuel, Periyasamy, and David have 
been promoted as committers to XCI.
You can see the nomination statements and the voting on Gerrit.

https://gerrit.opnfv.org/gerrit/#/q/status:merged+project:releng-xci+topic:xci-committer-promotion-skip-verify

I also want to take this opportunity to thank everyone for their contributions, 
support, and interest into XCI. Without them, XCI wouldn’t be where it is today.
Much more and even better things are coming so please stay tuned.

Helpdesk,

Please grant committer rights to new XCI committers on Gerrit releng-xci 
project.

/Fatih

From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Fatih 
Degirmenci <fatih.degirme...@ericsson.com>
Date: Wednesday, 21 March 2018 at 09:01
To: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [xci] Committer Nominations for releng-xci

Hi,

As approved by TSC on 2017-12-12 [1], it is my pleasure to nominate the XCI 
contributors listed below as committers to releng-xci Gerrit project.
XCI committers, please find the nomination statements on Gerrit changes linked 
below and cast your vote; +1/-1, directly on Gerrit.

Tianwei Wu: https://gerrit.opnfv.org/gerrit/#/c/53885/
Manuel Buil: https://gerrit.opnfv.org/gerrit/#/c/53887/
Periyasamy Palanisamy: https://gerrit.opnfv.org/gerrit/#/c/53889/
David Blaisonneau: https://gerrit.opnfv.org/gerrit/#/c/53891/

If the voting ends positively, I’ll inform the TSC regarding the promotions and 
ask helpdesk to grant committer rights in releng-xci Gerrit project to them.
[1] 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-12-12-14.01.html

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

[opnfv-tech-discuss] [xci] Committer Nominations for releng-xci

[Fatih Degirmenci]

Hi,

As approved by TSC on 2017-12-12 [1], it is my pleasure to nominate the XCI 
contributors listed below as committers to releng-xci Gerrit project.
XCI committers, please find the nomination statements on Gerrit changes linked 
below and cast your vote; +1/-1, directly on Gerrit.

Tianwei Wu: https://gerrit.opnfv.org/gerrit/#/c/53885/
Manuel Buil: https://gerrit.opnfv.org/gerrit/#/c/53887/
Periyasamy Palanisamy: https://gerrit.opnfv.org/gerrit/#/c/53889/
David Blaisonneau: https://gerrit.opnfv.org/gerrit/#/c/53891/

If the voting ends positively, I’ll inform the TSC regarding the promotions and 
ask helpdesk to grant committer rights in releng-xci Gerrit project to them.
[1] 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-12-12-14.01.html

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

[opnfv-tech-discuss] [releng] Voting on xci committer nominations

[Fatih Degirmenci]

Hi Releng Committers,

You might be aware of that we have a separate Gerrit project/repo for XCI, 
releng-xci, and the intention is to have separate set of committers for it. [1]
The current committers of releng-xci is subset of releng committers who have 
been actively contributing to XCI [2] and having Gerrit project/repo based 
committer list was approved by TSC. [3]

I would like to ask Releng committers to see if anyone has any objection to 
letting current releng-xci committers to vote on releng-xci committer 
promotions.

If you do, please raise your concern until March 20th.
If there is no objection, we will proceed by asking releng-xci committers to 
vote on committer promotions by this date.
Committer promotions for releng repo will be voted by releng committers so 
there is no change with that.

[1] https://gerrit.opnfv.org/gerrit/gitweb?p=releng-xci.git
[2] https://gerrit.opnfv.org/gerrit/gitweb?p=releng-xci.git;a=blob;f=INFO.yaml
[3] 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-12-12-14.01.html

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

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nToday’s meeting is cancelled due to un
 availability of several team members.\nTalk to you next week!\n\n/Fatih\n\
 nHi\,\n\nWelcome to OPNFV Cross Community CI (XCI) Meeting!\n\nYou can see
  the agenda for the upcoming meeting and the links to the minutes of the p
 revious meetings on https://etherpad.opnfv.org/p/xci-meetings\n\nPlease no
 te that this is an IRC-only meeting on #opnfv-pharos channel on freenode\,
  held on a weekly basis.\nPlease let me know in case if you want to have m
 eeting with voice/screen sharing to discuss/demo things in advance so we c
 an fix GTM for that meeting.\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/p
 ages/viewpage.action?pageId=8687635\nXCI @ OPNFV Jenkins: https://build.op
 nfv.org/ci/view/OPNFV%20XCI/\n\n/Fatih\n\n
UID:FF974A4D-2E66-4F48-B2FA-01361A607CD5
RECURRENCE-ID;TZID=W. Europe Standard Time:20180314T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180314T15
DTEND;TZID=W. Europe Standard Time:20180314T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180314T081430Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2116100340
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] [releng] Releng Graduation Proposal

[Fatih Degirmenci]

Hi,

Releng Graduation Proposal will be presented during Weekly Technical Community 
Discussion this Thursday. [1]

The slides have been uploaded to OPNFV Wiki. [2] Please feel free to update 
them so we can have them ready for the review this week.

[1] https://wiki.opnfv.org/display/PROJ/Weekly+Technical+Discussion
[2] 
https://wiki.opnfv.org/download/attachments/2925195/RelengGraduationProposal.pptx?api=v2

Thanks,
Fatih
___
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][security][infra] Anteater Improvements

[Fatih Degirmenci]

Hi Brian,

My comment wasn’t about the tools themselves but what they are used for and to 
be honest the suggestion is nothing sort of heavy-handed approach.

If someone includes something in an artifact that is consumed by someone else 
for different purposes, we have responsibility to them that we will always be 
able to recreate that artifact for different purposes such as troubleshooting.
If people hook their own machines to store artifacts that go into final OPNFV 
release and if these machines disappear, we will have no possibility to 
recreate what we released.
Apart from that, if people want to rebuild something for some reason, they will 
be unable to do that since the dependencies will not be available anymore.
These concerns are based on what we found while looking at our earlier releases 
so I’m not talking about something that’s possible to happen but a real issue 
that happened and we had to intervene.

If projects guarantee the long term availability of the artifacts on the 
original location (ie until the EOL of that specific release) and they ask for 
exception, there will be no blocking.

As you said, you are free to the promote tools and approaches like how I am 
doing here since I believe they are important to be shared.

/Fatih

From: "SULLIVAN, BRYAN L (BRYAN L)" <bryan.sulli...@research.att.com>
Date: Thursday, 8 March 2018 at 15:31
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>, Luke Hinds 
<lhi...@redhat.com>, "opnfv-tech-discuss@lists.opnfv.org" 
<opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

I do recommend that we rely upon tools that can focus on the trust of specific 
sources, and not the use of platform capabilities such as curl, wget, etc. 
These (curl, wget, etc) are tools that can be used for many purposes inside an 
application like an OPNFV platform, or its deployment/testing tools. The 
flagging/blocking of patches just because the code contains use of 
wget/curl/etc is an onerous and heavy-handed approach to the goal. Having to 
create regexp rules for each valid use of wget/curl is a non-starter for me and 
likely many others in this project. Thus I support Luke’s plan, and intend to 
promote these same tools and approaches for use in the Acumos and other LFN 
projects.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Fatih 
Degirmenci
Sent: Thursday, March 08, 2018 6:12 AM
To: Luke Hinds <lhi...@redhat.com>; opnfv-tech-discuss 
<opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Hi Luke,

I have few comments and followup questions regarding this:
“This in turn means we won't raise alarms over curl, git clone and wget and 
will instead check the IP addresses or URLS that those commands query. This 
should make anteater a lot less chatty at gate.”

You might remember that one of the reasons we have checks for curl/wget is to 
find out if projects pull artifacts from unknown IPs during 
build/deployment/testing.
These are not malicious but we have seen that few of the IPs where the projects 
fetch the artifacts belong to non-production/personal devices that tend to 
disappear over time.
As you know, this is an important issue from reproducibility and traceability 
perspectives.

Now the questions are;
Assuming the IPs are not explicitly added to exception list for the 
corresponding project, do you mean that we will stop flagging changes/files 
that contain wget/curl against unknown IPs if they are not marked as malicious 
on VirusTotal?
We also had plans to make anteater checks voting/blocking. Will we discard this 
plan since wget/curl against IPs are not even planned to be flagged?

/Fatih

From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Luke Hinds <lhi...@redhat.com<mailto:lhi...@redhat.com>>
Date: Thursday, 8 March 2018 at 14:02
To: 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

Hello,
I have some changes to improve the reporting ability and hopefully tone down 
the false positives.
Aneater will now interface with the VirusTotal public API:
1. If anteater finds a public IP address, the DNS history will be quiered to 
see if the IP has past or present associations with malicious domains.

2. If a URL is found, it is checked against the VirusTotal API to see if its 
marked as malicous.
3. Binaries will be sent to VirusTotal for a scan by the aggregation of 
scanners hosted there.
For anyone wanting a demo, please see the fo

Re: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

[Fatih Degirmenci]

Hi Luke,

I have few comments and followup questions regarding this:
“This in turn means we won't raise alarms over curl, git clone and wget and 
will instead check the IP addresses or URLS that those commands query. This 
should make anteater a lot less chatty at gate.”

You might remember that one of the reasons we have checks for curl/wget is to 
find out if projects pull artifacts from unknown IPs during 
build/deployment/testing.
These are not malicious but we have seen that few of the IPs where the projects 
fetch the artifacts belong to non-production/personal devices that tend to 
disappear over time.
As you know, this is an important issue from reproducibility and traceability 
perspectives.

Now the questions are;
Assuming the IPs are not explicitly added to exception list for the 
corresponding project, do you mean that we will stop flagging changes/files 
that contain wget/curl against unknown IPs if they are not marked as malicious 
on VirusTotal?
We also had plans to make anteater checks voting/blocking. Will we discard this 
plan since wget/curl against IPs are not even planned to be flagged?

/Fatih
From:  on behalf of Luke Hinds 

Date: Thursday, 8 March 2018 at 14:02
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

Hello,
I have some changes to improve the reporting ability and hopefully tone down 
the false positives.
Aneater will now interface with the VirusTotal public API:
1. If anteater finds a public IP address, the DNS history will be quiered to 
see if the IP has past or present associations with malicious domains.

2. If a URL is found, it is checked against the VirusTotal API to see if its 
marked as malicous.
3. Binaries will be sent to VirusTotal for a scan by the aggregation of 
scanners hosted there.
For anyone wanting a demo, please see the following:

https://asciinema.org/a/JfzUPWpBGm0wDKPCN3KlK2DK0
I will work with various people to get this rigged into CI.
This in turn means we won't raise alarms over curl, git clone and wget and will 
instead check the IP addresses or URLS that those commands query. This should 
make anteater a lot less chatty at gate.
Cheers,
Luke
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg] Xtesting is released

[Fatih Degirmenci]

Hi Cedric,

This is great to see! Many thanks to the Functest Team and everyone who 
contributed to this.
It will help us progress further with our cross-community collaboration efforts 
significantly.

/Fatih

On 2018-03-08, 11:19, "test-wg-boun...@lists.opnfv.org on behalf of 
cedric.olliv...@orange.com"  wrote:

Hello,

Functest team proudly announces the first publication of Xtesting.

Xtesting have leveraged on Functest efforts started from Euphrates
(python framework, docker slicing, dependency management, etc.) to
provide a reference testing framework allowing SDN/NFV testing on any
type of infrastructure.

In Fraser, Xtesting aims at allowing a smooth integration of our new
Kubernetes testcases and offers a possible reuse of our frameworks in
other OpenSource projects such as ONAP [1].

Xtesting could ease building any CI/CD toolchain for other domains than
testing VIM.

https://pypi.python.org/pypi/xtesting/0.23.0
https://hub.docker.com/r/opnfv/xtesting/tags/
http://xtesting.readthedocs.io/en/latest/apidoc/xtesting.html 

Functest, Functest-kubernetes and OPNFV Feature testcases have already
been adapted to leverage on it.
A special thank for all OPNFV Feature projects which merged quickly the
related gerrit changes.

Be free to run the default samples if you want a try:

via docker (you may note that the docker image is very "light" <100Mo)
$ sudo docker run opnfv/xtesting

via pip (python2)
$ virtualenv xtesting-py2
$ . xtesting-py2/bin/activate
$ pip install xtesting
$ sudo xtesting-py2/bin/run_tests -t all
$ deactivate

via pip (python3. Both are supported)
$ virtualenv xtesting-py3 -p python3
$ . xtesting-py3/bin/activate
$ pip install xtesting
$ sudo xtesting-py3/bin/run_tests -t all
$ deactivate

If needed, I can organize a session/discussion at ONS.

Cédric
Functest PTL

[1] https://wiki.onap.org/pages/viewpage.action?pageId=6593670=
%2F6593670%2F25433913%2Fintegration_demo_E2E_chain.pdf

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and 
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
test-wg mailing list
test...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/test-wg


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

Re: [opnfv-tech-discuss] [release]The strategy of screating the job for release branches

[Fatih Degirmenci]

Thanks for bringing this Tianwei.
I’ve been wondering the same thing since we started getting patches such as the 
one you linked below and need to review/submit them.

We had conversations to centralize job creation in synch with branching etc. 
but I’m not aware of any progress.

/Fatih

From: wutianwei <wutianw...@huawei.com>
Date: Thursday, 1 March 2018 at 09:42
To: "agard...@linuxfoundation.org" <agard...@linuxfoundation.org>, Trevor 
Bramwell <tbramw...@linuxfoundation.org>, "dmcbr...@linuxfoundation.org" 
<dmcbr...@linuxfoundation.org>, Fatih Degirmenci <fatih.degirme...@ericsson.com>
Cc: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [release]The strategy of screating the job for 
release branches

Hi all,

As we all know, MS5 is March 2nd where Jenkins jobs need to be created for all 
scenarios.
I wanted to know the strategy of creating the job for release branches.
Does it plan to create the jobs centrally? If not, we would submit the patch by 
ourselves.
https://gerrit.opnfv.org/gerrit/#/c/52085/

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

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\nThis week’s meeting is cancelled due t
 o PTG.\n\nDuring the meeting next week\, we will be discussing bringing Ko
 lla into XCI. Please have a look at the etherpad below and put your commen
 ts/questions.\n\nhttps://etherpad.opnfv.org/p/xci-kolla\n\n/Fatih\n\n
UID:FF974A4D-2E66-4F48-B2FA-01361A607CD5
RECURRENCE-ID;TZID=W. Europe Standard Time:20180228T15
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180228T15
DTEND;TZID=W. Europe Standard Time:20180228T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180226T101317Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2116100340
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Infra] Latest docs for connecting to Jenkins

[Fatih Degirmenci]

Hi Bryan,

The document is still valid but it needs a minor update; please install 
openjdk8 instead of 7.

We are in the process of moving infra docs into infra section on 
docs.opnfv.org and this document will be moved as well 
with any updates necessary.

When it comes to testing; the steps asking to execute the script will not work 
with your own/internal Jenkins since the script is specific to OPNFV Jenkins 
with hardcoded values. You can update the script with the details of your 
Jenkins master and try. Also you need to set slave connection type to jnlp 
instead of ssh while creating slaves on your Jenkins. Btw, ssh is the most 
common method for local setups where Jenkins master can reach slaves via ssh 
directly but we can’t use it due to 10+ remote labs - that’s why we have the 
script doing jnlp stuff.

/Fatih

On 12 Feb 2018, at 22:47, SULLIVAN, BRYAN L (BRYAN L) 
> wrote:

Is the document 
http://docs.opnfv.org/en/latest/submodules/octopus/docs/octopus_docs/opnfv-jenkins-slave-connection.html
 still valid?
I see very little info in the docs e.g. 
http://docs.opnfv.org/en/latest/infrastructure/ci.html, and need to know what 
is the current process for connecting to Jenkins, so I can first implement this 
internally, test it out, and then when ready connect to the OPNFV Jenkins.

Thanks,
Bryan Sullivan | AT

___
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] [test-wg]Requirements for test resources collection

[Fatih Degirmenci]

Hi Jack,

As Serena noted, all installers except Apex use same job structure; 1 
parent/upstream job starting and controlling the execution of the 
child/downstream jobs that do deployment, functest, and yardstick for a single 
scenario.
A variable can be generated by parent job and passed to child jobs so you can 
have one variable to identify a full run in the end.

This could be BUILD_TIMESTAMP as Trevor talked about below or something else as 
long as it is guaranteed to be unique within that installer or scenario.
What is important here is how you intend to push data to database. If you will 
track results on installer level than there is very small possibility of having 
same timestamp for 2 separate runs if they start exactly at the same time on 
millisecond.
In this case, UUID can be generated and used instead.

Another thing I missed mentioning is that you intend to link back to jobs on 
Jenkins if I understood it correctly. We have build retention policy on Jenkins 
so after certain period or no of builds (X days or Y no of builds), they get 
deleted and you will have links pointing to non-existing logs.
If you need to keep the logs then my suggestion would be to dump logs to 
somewhere that can also use the variable generated by the parent job so you 
have references to the things correctly.

/Fatih
 
On 2018-01-30, 08:22, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
chenjiankun" <opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
chenjiank...@huawei.com> wrote:

Hi Fatih & Trevor,

What we need is a new variable(like build_id) which can identify a 
combination of (Deployment + Functest + Yardstick) CI jobs. For example, if in 
one curtain scenario, we will run deployment job, Functest job and Yardstick 
job, and then their id will be the same.
Since I am not familiar with the Jenkins, can you give us some suggestions?
Or can you help us to add a new variable which can satisfy our requirements?
Thanks in advance~ 

BRs,
Jack Chan

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Trevor Bramwell
发送时间: 2018年1月30日 7:21
收件人: Fatih Degirmenci
抄送: Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources 
collection

Hi,

Previous versions of Jenkins set BUILD_ID to the timestamp of the build but 
now BUILD_ID = BUILD_NUMBER.

There are two plugins that appear to bring back 'BUILD_TIMESTAMP'[1][2].

It also wouldn't be too hard to generate this as part of a build step and 
we could keep the format TIMESTAMP_FORMAT as a global variable.

Regards,
Trevor Bramwell

[1] https://plugins.jenkins.io/build-timestamp
[2] https://plugins.jenkins.io/zentimestamp

On Tue, Jan 30, 2018 at 12:04:10AM +0100, Fatih Degirmenci wrote:
> Hi,
> 
> BUILD_ID should not be used for this type of purposes since it gets 
> reset when certain things happen such as
> 
> - recreation of jobs
> - migration to a new jenkins instance without preserving the build 
> history
> 
> If any of these things happen, there might be results with the same id 
> in db over time. It is better to find something else that never gets 
> reset such as timestamp.
> 
> /Fatih
> 
> On 29 Jan 2018, at 07:39, SerenaFeng(zte) 
> <serena.feng.711+...@gmail.com>
> wrote:
> 
> Hi Jack
> 
> Eventually, we hope all the installers push their deployment results 
> to TestAPI, in the current stage, we just leverage Daisy to have a try 
> and find a common framework to achieve that, we will promote it to 
> other installers soon after it works.
> 
> In terms of Jenkins id, almost all the installers leverage muti-job to 
> manage deployment and drive test projects. there is an entry job to 
> control all the jobs, such as 
> daisy-os-nosdn-nofeature-ha-baremetal-daily-master
> <https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-
> daily-master/>, maybe we can leverage the combination of the Jenkins 
> job and build_id
> daisy-os-nosdn-nofeature-ha-baremetal-daily-master_185
> <https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-
> daily-master/185/>(or jest the Jenkins job) to link to the Jenkins. As 
> for naming, instead of 'Jenkins' I would recommend using 'Job_name', 
> because, in zuulv3, Jenkins will be discarded, but the job idea will 
> be left(maybe in some other way)
> 
> For the status show, if only show the last and latest *one* iteration, 
> simple pass/fail is fine, or else multi-results will be included, I 
> don't rec

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[Fatih Degirmenci]

Hi,

BUILD_ID should not be used for this type of purposes since it gets reset
when certain things happen such as

- recreation of jobs
- migration to a new jenkins instance without preserving the build history

If any of these things happen, there might be results with the same id in
db over time. It is better to find something else that never gets reset
such as timestamp.

/Fatih

On 29 Jan 2018, at 07:39, SerenaFeng(zte) 
wrote:

Hi Jack

Eventually, we hope all the installers push their deployment results to
TestAPI, in the current stage, we just leverage Daisy to have a try and
find a common framework to achieve that, we will promote it to other
installers soon after it works.

In terms of Jenkins id, almost all the installers leverage muti-job to
manage deployment and drive test projects. there is an entry job to control
all the jobs, such as daisy-os-nosdn-nofeature-ha-baremetal-daily-master
,
maybe we can leverage the combination of the Jenkins job and build_id
daisy-os-nosdn-nofeature-ha-baremetal-daily-master_185
(or
jest the Jenkins job) to link to the Jenkins. As for naming, instead of
'Jenkins' I would recommend using 'Job_name', because, in zuulv3, Jenkins
will be discarded, but the job idea will be left(maybe in some other way)

For the status show, if only show the last and latest *one* iteration,
simple pass/fail is fine, or else multi-results will be included, I don't
recommend that. Personally, my suggestion is either integrate last one
iteration into last x iterations, all use statistics to show the results,
or separate into two pages: the current status(simple pass/fail) and the
history statistic status(8/9/10).

For Functest health check, Sure, Functest reports per execution result per
test case separately, we can get them from TestAPI, there's no problem with
that. But for health check actually includes 3 test
cases(connection_check/api_check/snaps_health_check), we need to cope with
that carefully.


BRs
Serena

On Sat, Jan 27, 2018 at 11:42 PM Julien  wrote:

> Hi Jack,
>
> I have finished the macro, but it failed for a Jenkins plugin is missing.
> I cc the issue email to you, which will be discussed in the infra meeting.
>
> BR/Julien
>
> David McBride 于2018年1月27日周六 上午12:13写道：
>
>> +Julien
>>
>> Jack,
>>
>> I like the table format and the filtering options that you proposed.
>> Also +1 to Serena's suggestion to break out the health check data.
>>
>> I think that Julien is working on a Jenkins macro to enable the test API
>> to retrieve the "jenkins id".  Julien - please confirm.
>>
>> David
>>
>> On Tue, Jan 23, 2018 at 10:53 PM, chenjiankun 
>> wrote:
>>
>>> Hi Serena,
>>>
>>>
>>>
>>> Thanks for your information updating.
>>>
>>> I am so glad to see TestAPI is ready to collecting deployment results,
>>> and it would be much more convenient.
>>>
>>> One question: does all installer will push result to DB, or just Daisy
>>> for now?
>>>
>>>
>>>
>>> For the Jenkins id, it means a combination of deployment + functest +
>>> yardstick job. I am not sure if there are a ‘jenkins_id’ for now. This
>>> field is for identify the combination jobs.
>>>
>>> For the second comment, maybe there are some misunderstanding, as
>>> David’s requirements, we will show data last x iterations(not days), so I
>>> think there will be no such problems.
>>>
>>> For the healthcheck column, I totally agree with you. But maybe it will
>>> depend on functest to upload test result independently.
>>>
>>>
>>>
>>> What’s your opinions? @David, @Serena
>>>
>>>
>>>
>>> BRs,
>>>
>>> Jack Chan
>>>
>>>
>>>
>>> *发件人:* SerenaFeng(zte) [mailto:serena.feng.711+...@gmail.com]
>>> *发送时间:* 2018年1月22日 18:08
>>> *收件人:* chenjiankun
>>> *抄送:* David McBride; Serena Feng; TECH-DISCUSS OPNFV
>>> *主题:* Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources
>>> collection
>>>
>>>
>>>
>>> Hi David & Jack,
>>>
>>>
>>>
>>> Thanks for mentioning the task, an interface for collecting deployment
>>> results has been ready in TestAPI[1],
>>>
>>> the Macro for pushing deployment result is also ready by Jelien[2], I
>>> believe it will facilitate all the installers' work,
>>>
>>> currently, Julien is working on pushing daisy results to TestAPI
>>> leveraging that Macro, I think it will be finished soon.
>>>
>>>
>>>
>>> And regarding how to show all the information in a table, I suggest we
>>> can take a look at Jack's proposal first.
>>>
>>>
>>>
>>> @Jack, a few comments:
>>>
>>> 1. what's the opinion of jenkins id?
>>>
>>> 2. for a scenario-installer combination, some will not run once in a
>>> day(trigger multiple times or run in multiple pods),
>>>
>>> in this case, a simple pass/fail will be too vague, and to
>>> facilitate the support of data 

[opnfv-tech-discuss] [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting (15:00 UTC) and the meeting tool we will be using.\n\n\n\n
 The "Infra Working Group" plans and tracks infrastructure cross project in
 itiatives.\n\n\nWe report our efforts up to the TSC to ensure the communit
 y is able to provide sufficient resources for development and release infr
 astructure.\n\n\n\nTopics and meeting agenda at https://wiki.opnfv.org/dis
 play/INF/Infra+Working+Group\n\nMinutes at Infra Working Group Meeting\n\n\n\nP
 lease download and import the following iCalendar (.ics) files to your cal
 endar system.\n\nWeekly: https://zoom.us/meeting/156937927/ics?icsToken=0e
 174b418dee2290306aef52a929342f9984a2cdf1f0072e149682294c21350c\n\n\n\nJoin
  from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/156937927\n\n\n
 \nOr iPhone one-tap :\n\nUS: +16699006833\,\,156937927#  or +164655886
 56\,\,156937927#\n\nOr Telephone:\n\nDial(for higher quality\, dial a 
 number based on your current location):\n\nUS: +1 669 900 6833  or
  +1 646 558 8656\n\nMeeting ID: 156 937 927\n\nInternational numbe
 rs available: https://zoom.us/zoomconference?m=RQv_-YV6NntsxKLfD8YglXwk4Av
 wrNK4\n\n\n\n/Fatih\n
RRULE:FREQ=WEEKLY;UNTIL=20180305T15Z;INTERVAL=1;BYDAY=MO;WKST=SU
UID:E51AA012-65CA-4BD0-88C6-4D46EE1AC7F5
SUMMARY;LANGUAGE=en-US:[Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20180129T15
DTEND;TZID=UTC:20180129T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180125T101006Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:Zoom (https://zoom.us/j/156937927) and IRC #opnfv-m
 eeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116145084
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"Zoom (https://zoom.us/j/156937927) a
 nd IRC #opnfv-meeting"\,"LocationAnnotation":""\,"LocationUri":""\,"Locati
 onStreet":""\,"LocationCity":""\,"LocationState":""\,"LocationCountry":""\
 ,"LocationPostalCode":""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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

Re: [opnfv-tech-discuss] [releng-xci] XCI documentation for OPNF Docs hackfest?

[Fatih Degirmenci]

Hi Tapio,

That would be really helpful.

About the way of working; it wasn't migrated to docs.opnfv.org intentionally 
since we were trying to see if the way we envisioned would work. (specific 
scenarios are developed in the project repos who own them and XCI provides 
framework for them)
I think we successfully demonstrated that this way of working will work pretty 
well. Please see the documentation on Wiki which we need to move relevant parts 
of it to docs.opnfv.org as soon as we can. [1]

Developer Guide will have 2 main sections; first one is for the XCI Framework 
developers which your experience while working with Centos support is pretty 
relevant here.
The other section is for the projects who (wish to) onboard their 
scenarios/features to XCI. This section will have references to way of working 
but will go into more technical details.

[1] https://wiki.opnfv.org/pages/viewpage.action?pageId=12390152

/Fatih

On 2018-01-25, 09:38, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
Tallgren, Tapio (Nokia - FI/Espoo)"  wrote:

Hi Fatih, Marcos et al.,

I am planning to participate in the OPNFV Docs Hackfest on Feb 1st and I 
was wondering if I could help with the XCI documentation. The XCI Overview and 
XCI Sandbox seem to be in pretty good shape, the Way of Working I have no idea 
about, and the Developer Guide is mostly missing. Would it make sense for me to 
write down some lessons learned there? Other ideas?

-Tapio 
___
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] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\nCancelling today’s meeting since there
  is not much to update comparing to the last week.\n\nTalk to you all next
  week.\n\n/Fatih\n\nHi\,\n\nWelcome to OPNFV Cross Community CI (XCI) Meet
 ing!\n\nYou can see the agenda for the upcoming meeting and the links to t
 he minutes of the previous meetings on https://etherpad.opnfv.org/p/xci-me
 etings\n\nPlease note that this is an IRC-only meeting on #opnfv-pharos ch
 annel on freenode\, held on a weekly basis.\nPlease let me know in case if
  you want to have meeting with voice/screen sharing to discuss/demo things
  in advance so we can fix GTM for that meeting.\n\nXCI @ OPNFV Wiki: https
 ://wiki.opnfv.org/pages/viewpage.action?pageId=8687635\nXCI @ OPNFV Jenkin
 s: https://build.opnfv.org/ci/view/OPNFV%20XCI/\n\n/Fatih\n\n
UID:FF974A4D-2E66-4F48-B2FA-01361A607CD5
RECURRENCE-ID;TZID=W. Europe Standard Time:20180117T15
SUMMARY;LANGUAGE=en-GB:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180117T15
DTEND;TZID=W. Europe Standard Time:20180117T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180117T124205Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2116100340
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Pharos] Stepping down as PTL

[Fatih Degirmenci]

Hi,

+2.

Welcome Julien. Looking forward to your guidance and support with Infra!

Jack,

It’s been a pleasure working with you and facing/tackling all the challenges 
together. We made a lot of progress when it comes to Infra, thanks to your 
leadership and contributions.
Apart from OPNFV itself, you have been very important to cross-community 
collaboration and helped us a lot to keep things moving.

Also, I am grateful for your patience, positive attitude and more importantly 
for your friendship.
I will continue bugging you with my endless complaints no matter how much you 
stay involved in OPNFV because I know I’ll get the help when needed.

Thank you.

/Fatih

From:  on behalf of Jack Morgan 

Date: Wednesday, 17 January 2018 at 08:07
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [Pharos] Stepping down as PTL


OPNFV,

It is with great sorrow that I'm announcing that I will be stepping down as the 
Pharos PTL. It has been nearly two years since I took over the PTL role and I 
hope my contributions have been beneficial. I really appreciate all the help 
and support I've received from the community. I feel I've really gained from 
the experience.

In the meanwhile, I would like to nominate Julien Zhang as the next Pharos PTL. 
He has been very active in the Pharos project this past year not just with 
gerrit patches, but also in documentation, Infra WG meetings and other Pharos 
projects.



Committers, please vote +2/-2 for Julien as Pharos PTL.



Thanks,

--

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

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nYou can see the agenda for the upcoming meeting and 
 the links to the minutes of the previous meetings on https://etherpad.opnf
 v.org/p/xci-meetings\n\n\n\nPlease note that this is an IRC-only meeting o
 n #opnfv-pharos channel on freenode\, held on a weekly basis.\n\nPlease le
 t me know in case if you want to have meeting with voice/screen sharing to
  discuss/demo things in advance so we can fix GTM for that meeting.\n\n\n\
 nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId=868
 7635\n\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/\
 n\n\n\n/Fatih\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180321T14Z;INTERVAL=1;BYDAY=WE;WKST=SU
UID:FF974A4D-2E66-4F48-B2FA-01361A607CD5
SUMMARY;LANGUAGE=en-GB:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20180110T15
DTEND;TZID=W. Europe Standard Time:20180110T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180104T095143Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116100340
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"IRC-only (#opnfv-pharos on freenode)
 "\,"LocationAnnotation":""\,"LocationUri":""\,"LocationStreet":""\,"Locati
 onCity":""\,"LocationState":""\,"LocationCountry":""\,"LocationPostalCode"
 :""\,"LocationFullAddress":""}]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\nThe next Infra WG Meeting is on January 
 8th\, 2018.\n\nMerry Christmas and Happy New Year!\n\n/Fatih\n\nHi\,\n\nPl
 ease note the change in start time of the meeting\, 16:00 UTC.\nThis is to
  prevent conflicts between Infra WG Meeting and OPNFV Plugfest Planning Me
 eting. (Some) Infra WG Meeting participants join the plugfest planning cal
 l as well.\n\nThe "Infra Working Group" plans and tracks infrastructure cr
 oss project initiatives.\n\nWe report our efforts up to the TSC to ensure 
 the community is able to provide sufficient resources for development and 
 release infrastructure.\n\nTopics and meeting agenda at https://wiki.opnfv
 .org/display/INF/Infra+Working+Group\nMinutes at Infra Working Group Meeti
 ng<https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting>\n\
 nWeekly on Monday at 16:00 UTC\nGTM Link https://global.gotomeeting.com/jo
 in/819733085\nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\nC
 haired by Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a
  2-month basis)\nYou can also dial in using your phone with Access Code: 8
 19-733-085\n\nUnited States +1 (312) 757-3126\nAustralia +61 2 8355 1040\n
 Austria +43 7 2088 0034\nBelgium +32 (0) 28 93 7018\nCanada +1 (647) 497-9
 350\nDenmark +45 69 91 88 64\nFinland +358 (0) 923 17 0568\nFrance +33 (0)
  170 950 592\nGermany +49 (0) 692 5736 7211\nIreland +353 (0) 15 360 728\n
 Italy +39 0 247 92 13 01\nNetherlands +31 (0) 208 080 219\nNew Zealand +64
  9 280 6302\nNorway +47 75 80 32 07\nSpain +34 911 82 9906\nSweden +46 (0)
  853 527 836\nSwitzerland +41 (0) 435 0167 13\nUnited Kingdom +44 (0) 330 
 221 0086\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171225T16
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171225T16
DTEND;TZID=UTC:20171225T17
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171224T085644Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:10
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Use of #lf-releng for Releng Support

[Fatih Degirmenci]

Hi Ozgur,

Yes, it is on Freenode IRC.

/Fatih

From: Ozgur <okara...@yandex.com>
Date: Tuesday, 12 December 2017 at 21:49
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>, 
"opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Use of #lf-releng for Releng Support

Hello Fatih,

is the channel on Freenode? which irc server?

Regards,

Ozgur

12.12.2017, 15:48, "Fatih Degirmenci" <fatih.degirme...@ericsson.com>:

Hi,



We decided to use common IRC channel #lf-releng for Releng Support issues so we 
can get help from our friends who work with other LF Networking Projects and 
increase the collaboration.



Please get in touch with us on that channel for faster response. Few of us are 
already there.

Automatic redirection from #opnfv-octopus to #lf-releng will soon be enabled.



/Fatih
,

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto: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] Use of #lf-releng for Releng Support

[Fatih Degirmenci]

Hi,

We decided to use common IRC channel #lf-releng for Releng Support issues so we 
can get help from our friends who work with other LF Networking Projects and 
increase the collaboration.

Please get in touch with us on that channel for faster response. Few of us are 
already there.
Automatic redirection from #opnfv-octopus to #lf-releng will soon be enabled.

/Fatih
___
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] Committer list per Releng repository

[Fatih Degirmenci]

Hi Frank,

Thanks for the feedback.

Splitting Releng is perhaps an option but I personally do not think it will add 
too much value. 
I believe support functions such as what Releng aims to provide is best handled 
as a whole rather than multiple individual projects.
This is important in order to ensure the project provides best service to the 
community and sub teams follow overall direction set by Infra WG in general and 
Releng Project in particular.

With that said, if any Releng committer comes up with a proposal to split 
Releng, resulting in multiple smaller projects, we can put these 2 proposals to 
vote and do accordingly.

Another thing I would like to highlight is that the proposed setup with 
subprojects/teams is pretty similar to how OpenStack Infra project works; top 
level Infra project and multiple sub teams that specialize in certain aspects 
of the infra. [1]
We as project need to work on the details if this proposal is accepted and 
approved by the TSC. Until this happens, that link can give an idea regarding 
where we might end up. 

One last point is, Releng will probably not be the only one with this need. We 
are just the first one.

[1] https://docs.openstack.org/infra/system-config/project.html#teams

/Fatih

On 2017-12-11, 03:03, "Frank Brockners (fbrockne)" <fbroc...@cisco.com> wrote:

Hey folks,

Have we considered making these just 5 separate projects (which basically 
what they are)? That'd fit the OPNFV structure, gives each project a dedicated 
repo (which they have already), and a dedicated set of committers plus a PTO...

Frank

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Trevor Bramwell
Sent: Sonntag, 10. Dezember 2017 15:34
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>
Cc: Serena Feng <feng.xiao...@zte.com.cn>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng 
repository

+1

Giving leaders of subproject the freedom to manage +2 rights on their own 
repository will be very helpful for ensuring patches are reviewed by those with 
the correct competencies and merged in a timely manner.

Perhaps having a 'mini-info' file in each repository would help track this, 
intead of expanding the current INFO file. Simple fields such as:
parent-project, project-name, creation-date, subproject-lead, committers, 
and parent-project-approval-link would work. This is merely a suggestion 
though, and a decision on this shouldn't block us from moving forward. I'm fine 
with things currently being added the INFO file.

Regards,
Trevor Bramwell

On Fri, Dec 08, 2017 at 12:01:34AM +, Fatih Degirmenci wrote:
> Hi Releng Committers,
> 
> During OPNFV Plugfest, we had conversations around having committer list 
per Releng repository/Gerrit Project.
> 
> The reason behind this is that, Releng project currently has 5 
> different repositories as listed below. [1]
> 
> 
>   *   releng
>   *   releng-anteater
>   *   releng-testresults
>   *   releng-utils
>   *   releng-xci
> 
> The work that is done in these repositories require different competence 
profiles. For example for releng repository, the committers need to have 
knowledge in CI, Jenkins, Jenkins Job Builder and so on.
> Apart from the required competence, some developers might not be 
interested in certain parts of Releng but interested in others.
> 
> Having single committer list across all Releng owned repositories 
prevents us from recognizing contributors and promoting them as committers for 
the corresponding repositories since they will perhaps never have enough 
contributions across all of them.
> Another limitation is that, the current review practices followed by 
Releng is not good and we need to improve this. Having right set of committers 
per repo and getting patches reviewed by them properly will help with the 
quality of work we are doing.
> 
> In order to address this limitation and have the ability and the 
possibility to recognize and promote developers who made great contributions to 
Releng in general in the repositories they worked in, I propose to create 
committer list per repo.
> 
> Please respond to this mail with +1 and -1 and share questions, comments, 
concerns if you have any.
> 
> I plan to bring this topic to TSC on December 12th if the vote passes.
> 
> [1] https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng
> 
> /Fatih
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-te

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

[Fatih Degirmenci]

Hi Ryota,

Introducing sub-team lead was part of our conversation today and we will work 
on it when/if our proposal gets agreed within Releng project and approved by 
TSC.

/Fatih

From: Ryota <r-m...@cq.jp.nec.com>
Date: Thursday, 7 December 2017 at 16:16
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>, 
"agard...@linuxfoundation.org" <agard...@linuxfoundation.org>, 'Tim Rozet' 
<tro...@redhat.com>, Morgan Richomme <morgan.richo...@orange.com>, Jose Lausuch 
<jalaus...@suse.com>, Meimei <mei...@huawei.com>, Trevor Bramwell 
<tbramw...@linuxfoundation.org>, Serena Feng <feng.xiao...@zte.com.cn>, Yolanda 
Mota <yrobl...@redhat.com>, Markos Chandras <mchand...@suse.de>, Luke Hinds 
<lhi...@redhat.com>
Cc: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [releng] Committer list per Releng repository

+1

Also we need to consider long term transition. Each repo or sub-team would be 
getting bigger then could be independent project/repo eventually. So, it would 
be nice to find sub-team lead or key person who is responsible in each repo 
along with this list modification. Just two cents though.

BR,
Ryota

From: Fatih Degirmenci [mailto:fatih.degirme...@ericsson.com]
Sent: Friday, December 08, 2017 9:02 AM
To: Aric Gardner <agard...@linuxfoundation.org>; Tim Rozet <tro...@redhat.com>; 
Morgan Richomme <morgan.richo...@orange.com>; Jose Lausuch 
<jalaus...@suse.com>; Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com>; Meimei 
<mei...@huawei.com>; Trevor Bramwell <tbramw...@linuxfoundation.org>; Serena 
Feng <feng.xiao...@zte.com.cn>; Yolanda Robla Mota <yrobl...@redhat.com>; 
Markos Chandras <mchand...@suse.de>; Luke Hinds <lhi...@redhat.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [releng] Committer list per Releng repository

Hi Releng Committers,

During OPNFV Plugfest, we had conversations around having committer list per 
Releng repository/Gerrit Project.

The reason behind this is that, Releng project currently has 5 different 
repositories as listed below. [1]


  *   releng
  *   releng-anteater
  *   releng-testresults
  *   releng-utils
  *   releng-xci

The work that is done in these repositories require different competence 
profiles. For example for releng repository, the committers need to have 
knowledge in CI, Jenkins, Jenkins Job Builder and so on.
Apart from the required competence, some developers might not be interested in 
certain parts of Releng but interested in others.

Having single committer list across all Releng owned repositories prevents us 
from recognizing contributors and promoting them as committers for the 
corresponding repositories since they will perhaps never have enough 
contributions across all of them.
Another limitation is that, the current review practices followed by Releng is 
not good and we need to improve this. Having right set of committers per repo 
and getting patches reviewed by them properly will help with the quality of 
work we are doing.

In order to address this limitation and have the ability and the possibility to 
recognize and promote developers who made great contributions to Releng in 
general in the repositories they worked in, I propose to create committer list 
per repo.

Please respond to this mail with +1 and -1 and share questions, comments, 
concerns if you have any.

I plan to bring this topic to TSC on December 12th if the vote passes.

[1] https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng

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

[opnfv-tech-discuss] [releng] Committer list per Releng repository

[Fatih Degirmenci]

Hi Releng Committers,

During OPNFV Plugfest, we had conversations around having committer list per 
Releng repository/Gerrit Project.

The reason behind this is that, Releng project currently has 5 different 
repositories as listed below. [1]


  *   releng
  *   releng-anteater
  *   releng-testresults
  *   releng-utils
  *   releng-xci

The work that is done in these repositories require different competence 
profiles. For example for releng repository, the committers need to have 
knowledge in CI, Jenkins, Jenkins Job Builder and so on.
Apart from the required competence, some developers might not be interested in 
certain parts of Releng but interested in others.

Having single committer list across all Releng owned repositories prevents us 
from recognizing contributors and promoting them as committers for the 
corresponding repositories since they will perhaps never have enough 
contributions across all of them.
Another limitation is that, the current review practices followed by Releng is 
not good and we need to improve this. Having right set of committers per repo 
and getting patches reviewed by them properly will help with the quality of 
work we are doing.

In order to address this limitation and have the ability and the possibility to 
recognize and promote developers who made great contributions to Releng in 
general in the repositories they worked in, I propose to create committer list 
per repo.

Please respond to this mail with +1 and -1 and share questions, comments, 
concerns if you have any.

I plan to bring this topic to TSC on December 12th if the vote passes.

[1] https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng

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

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Markos Ch
 andras:MAILTO:mchand...@suse.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Yolanda M
 ota:MAILTO:yrobl...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jack Morg
 an:MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Manuel Bu
 il:MAILTO:mb...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=wutianwei
 :MAILTO:wutianw...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Nikolas H
 ermanns:MAILTO:nikolas.herma...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=BLAISONNE
 AU RD-CORE-LAN:MAILTO:david.blaisonn...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=mardim@in
 tracom-telecom.com:MAILTO:mar...@intracom-telecom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Bob Monk
 man':MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=zhang.jun
 3...@zte.com.cn:MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=fangfang 
 (C):MAILTO:fangfa...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Periyasam
 y Palanisamy:MAILTO:periyasamy.palanis...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Stephen W
 ong:MAILTO:stephen.wo...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=tapio.tal
 lg...@nokia.com:MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Dave Ursc
 hatz:MAILTO:dave.ursch...@cengn.ca
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=taseer94@
 gmail.com:MAILTO:tasee...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\nMeeting on December 6th is cancelled due
  to Plugfest.\n\n/Fatih\n\n\nHi\,\n\nWelcome to OPNFV Cross Community CI (
 XCI) Meeting!\n\nYou can see the agenda for the upcoming meeting on https:
 //etherpad.opnfv.org/p/xci-meetings\n\nPlease note that this is an IRC-onl
 y meeting on #opnfv-pharos channel held on a weekly basis.\nPlease let me 
 know in case if you want to have meeting with voice/screen sharing to disc
 uss/demo things in advance so I can fix GTM for that meeting.\n\nXCI @ OPN
 FV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId=8687635\nXCI 
 @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI/\n\n/Fatih\n
UID:580EB2B8-73C8-440B-9F2D-6CF66601334A
RECURRENCE-ID;TZID=W. Europe Standard Time:20171206T15
SUMMARY;LANGUAGE=en-GB:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20171206T15
DTEND;TZID=W. Europe Standard Time:20171206T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171205T161330Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:4
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:2115460920
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\nMeeting on December 4th is cancelled due
  to Plugfest. See you in Portland!\n\n/Fatih\n\n\nHi\,\n\nPlease note the 
 change in start time of the meeting\, 16:00 UTC.\nThis is to prevent confl
 icts between Infra WG Meeting and OPNFV Plugfest Planning Meeting. (Some) 
 Infra WG Meeting participants join the plugfest planning call as well.\n\n
 The "Infra Working Group" plans and tracks infrastructure cross project in
 itiatives.\n\nWe report our efforts up to the TSC to ensure the community 
 is able to provide sufficient resources for development and release infras
 tructure.\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/I
 NF/Infra+Working+Group\nMinutes at Infra Working Group Meeting\n\nWeekly on Mon
 day at 16:00 UTC\nGTM Link https://global.gotomeeting.com/join/819733085\n
 IRC #opnfv-meeting - freenode.net\n\nChaired by Fati
 h Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month basis
 )\nYou can also dial in using your phone with Access Code: 819-733-085\n\n
 United States +1 (312) 757-3126\nAustralia +61 2 8355 1040\nAustria +43 7 
 2088 0034\nBelgium +32 (0) 28 93 7018\nCanada +1 (647) 497-9350\nDenmark +
 45 69 91 88 64\nFinland +358 (0) 923 17 0568\nFrance +33 (0) 170 950 592\n
 Germany +49 (0) 692 5736 7211\nIreland +353 (0) 15 360 728\nItaly +39 0 24
 7 92 13 01\nNetherlands +31 (0) 208 080 219\nNew Zealand +64 9 280 6302\nN
 orway +47 75 80 32 07\nSpain +34 911 82 9906\nSweden +46 (0) 853 527 836\n
 Switzerland +41 (0) 435 0167 13\nUnited Kingdom +44 (0) 330 221 0086\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171204T16
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171204T16
DTEND;TZID=UTC:20171204T17
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171130T154459Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:9
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Infra] Request for a StorPerf pod

[Fatih Degirmenci]

Hi Mark,

Can you please put this request to JIRA INFRA project so we can follow it up 
properly?
We can include this as a topic to Infra WG Meeting so please keep an eye on the 
meeting agenda and join if possible.

Please note that we haven’t decided if we will have the Infra WG Meeting on 
December 4th due to OPNFV Plugfest so your ticket might be discussed on 
December 11th – if you still don’t have a BM POD/vPOD by then.

/Fatih

From:  on behalf of "Beierl, Mark" 

Date: Wednesday, 29 November 2017 at 15:15
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [Infra] Request for a StorPerf pod

Hello,

Since Intel is no longer able to provide their pod 24 for StorPerf, we are now 
in the position of seeing if there is any other pod or vpod that we can use for 
StorPerf development and testing.  Please let me know what the procedure is to 
request a new pod.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
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] [Infra] Infra WG Meeting Minutes - Nov 20th

[Fatih Degirmenci]

November 20

Minutes 
(link<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-11-20-16.00.html>)

  1.  Zuulv3 Prototype
 *   A VM has been brought up to start the prototype. More info to follow 
once we have some progress.
  2.  Huawei Lab
 *   Huawei lab will be migrated during this week
 *   Impacted resources are huawei-pod7, huawei-pod12, huawei-virtual5 and 
huawei-virtual7
 *   The impacted resources will be offline during the migration
 *   Impacted projects are Compass and Joid
 *   An ARM based POD will be added as well
  3.  CI Resources for JOID
 *   JOID doesn't have any resources to run baremetal jobs
 *   intel-pod18 has been made available to JOID and it needs to be 
connected to OPNFV Jenkins
 *   To connect this POD to OPNFV Jenkins, a mail to opnfv-helpdesk is 
needed and the workaround needs to be applied for port 80
 *   Once the POD is connected to Jenkins, it needs to be labelled with 
joid-baremetal
 *   And finally the slave needs to be added to slave-params.yml
 *   
https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/global/slave-params.yml
  4.  XCI at Plugfest
 *   XCI session is scheduled for Day 3
 *   
https://wiki.opnfv.org/display/EVNT/Euphrates+Plugfest+Schedule#EuphratesPlugfestSchedule-Day3(December6th)Schedule
 *   Practices/principles to follow in order to be part of XCI need to be 
agreed on
 *   Infra/CI practices such as PDF/IDF/SDF & dynamic CI, having people/hw, 
etc. which will be documented
  5.  How to use special HW and test accordingly
 *   Some features require special hw or specific configuration which need 
to be handled
 *   Discussion is needed to find out how to work on this
 *   One option could be incorporating this into ongoing discussion to 
refresh Pharos spec
 *   This is needed in order to easily find out which features are offered 
by which labs/PODs
 *   Based on the information provided by the labs, we can automatically 
decide where a certain deployment should go or enable test frameworks to pick 
right test cases
 *   Pharos spec can have some basic use cases and the above things could 
be additions on top of the base spec
 *   A topic for plugfest has been added to the agenda: Testing 
hardware/software interactions brainstorming
 *   
https://wiki.opnfv.org/display/EVNT/Euphrates+Plugfest+Schedule#EuphratesPlugfestSchedule-Day4(December7th)Schedule
 *   The day/time of the session might change coming days
  6.  Define test requirements for gating scenarios for the release
 *   This is simply improving release criteria by using the results from 
test runs
 *   Tooling support is needed
 *   Release Criteria needs to be discussed and brought up to TSC for 
approval once things are clarified within community
  7.  Action Items
 *   NEW: Contact projects that are affected by Huawei Lab Move. 
wutianwei<https://wiki.opnfv.org/display/~wutianwei> and Fatih 
Degirmenci<https://wiki.opnfv.org/display/~fdegir>
 *   NEW: Connect and get the slave for intel-pod18 operational on OPNFV 
Jenkins. Narinder Gupta<https://wiki.opnfv.org/display/~narindergupta> and 
Trevor Bramwell<https://wiki.opnfv.org/display/~bramwelt>
 *   NEW: Follow up the topic regarding the use of special HW and test 
accordingly during Plugfest. Tim 
Irnich<https://wiki.opnfv.org/display/~timirnich>
 *   NEW: Follow up the topic regarding defining the test requirements for 
gating scenarios for the release during Plugfest. David 
McBride<https://wiki.opnfv.org/display/~dmcbride>
 *   NEW: Decide how to handle Pharos/HW Infra documentation - will it be 
part of Infra space on docs.opnfv.org or something else. Jack 
Morgan<https://wiki.opnfv.org/display/~jmorgan1>
 *   DONE: Add topic regarding PDF/IDF/SDF into OPNFV Plugfest/Hackfest 
agenda Fatih Degirmenci<https://wiki.opnfv.org/display/~fdegir>
 *   DONE: Contact Ulrich Kleber<https://wiki.opnfv.org/display/~ulik> 
regarding the retirement/archival of Octopus project. Fatih 
Degirmenci<https://wiki.opnfv.org/display/~fdegir> and Ray 
Paik<https://wiki.opnfv.org/display/~rpaik>
 *   DONE: Contact David McBride<https://wiki.opnfv.org/display/~dmcbride> 
about having Security as part of a release process by adding it to relevant 
Milestone(s). Luke Hinds<https://wiki.opnfv.org/display/~lukehinds> and Fatih 
Degirmenci<https://wiki.opnfv.org/display/~fdegir>
 *   DONE: Ask OPNFV TSC about the Zuulv3 prototype requirements. Trevor 
Bramwell<https://wiki.opnfv.org/display/~bramwelt>
 *   DONE: Send list of available unblocked ports to Aric 
Gardner<https://wiki.opnfv.org/display/~admin> for new Jenkins server. Jack 
Morgan<https://wiki.opnfv.org/display/~jmorgan1>
 *   DONE: Send email to Lab owners to request them to inp

[opnfv-tech-discuss] [infra][releng] Proposal to use #lf-releng IRC Channel for OPNFV Releng

[Fatih Degirmenci]

Hi,

There is a proposal from OpenDaylight community to redirect Releng channels to 
#lf-releng so we can have the Jenkins, JJB, Gerrit, etc. related discussions 
there together with other sister projects.
Please see the thread on

https://lists.opnfv.org/pipermail/infra-wg/2017-October/83.html

I believe this is beneficial for all of us and we will be discussing this topic 
during the next Infra WG Meeting on November 27th.
Please join to the meeting if you have feedback or concerns about the proposal 
so we discuss it there and take a decision.

https://wiki.opnfv.org/display/INF/Infra+Working+Group

/Fatih

From:  on behalf of Thanh Ha 

Date: Wednesday, 4 October 2017 at 01:01
To: "disc...@lists.fd.io" , "t...@lists.fd.io" 
, vpp-dev , "csit-...@lists.fd.io" 
, "onap-disc...@lists.onap.org" 
, "infra...@lists.opnfv.org" 

Cc: odl-dev-list 
Subject: Re: [infra-wg] [releng] Proposal to redirect #opendaylight-releng to 
#lf-releng

On Tue, Sep 26, 2017 at 6:38 PM, Thanh Ha 
> wrote:
Hi Everyone,

We'd like to pitch an idea to have #opendaylight-releng irc channel redirect to 
a new #lf-releng channel. Something that's occurred to us is that many of the 
networking at LF projects have their own separate releng channels in which 
folks typically ask JJB related questions. Each of these channels are typically 
moderately active.

Something we've been thinking about is the idea of merging all these releng 
channels into #lf-releng which we're hoping can combine the communities JJB 
experts so that JJB and other releng related questions can be more broadly 
asked.

Thoughts?

Regards,
Thanh

Hi Everyone,

For those that don't know me. I am one of the release engineers working on the 
OpenDaylight project. I've added the fd.io, opnfv, and onap 
communities to this list to get feedback on the idea proposed above. Let me 
know if there's other mailing lists in the respective projects we should be 
cc'ing to include in the discussions.

I'd like to hear from the fd.io, opnfv, and onap for their 
thoughts on the proposal to create a single lf-releng channel on IRC and have 
all the respective releng channels redirect to it. Since our respective releng 
projects use similar technologies like JJB, Jenkins, etc... it might be a 
benefit to pool together our expertise so that it is easier to ask questions to 
the broader community when we need help with things like JJB, Gerrit, etc...

You can follow the discussion thread so far from the ODL community discussed 
here:
https://lists.opendaylight.org/pipermail/dev/2017-September/004066.html


Regards,
Thanh

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

[opnfv-tech-discuss] [Infra] Infra WG Meeting Minutes - Nov 13th

[Fatih Degirmenci]

November 13

Minutes 
(link<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-11-13-16.00.html>)


  1.  Status Updates:
 *   PDF/IDF

*   PDF/IDF has been in use by different installers such as Fuel/MCP, 
Daisy, OSA.
*   Apex team started looking into PDF/IDF to see if what is there 
covers their needs.
*   No updates from Joid.
 *   LaaS and Dashboard integration
*   UNH has been working on this and we need to check the latest status 
with them.
*   Trevor Bramwell<https://wiki.opnfv.org/display/~bramwelt> and 
Parker Berberian<https://wiki.opnfv.org/display/~ParkerBerberian> enabled 
showing CI PODs on Dashboard.
 *   Infra Documentation on RTD (docs.opnfv.org)
*   Patch<https://gerrit.opnfv.org/gerrit/#/c/45089/> moving CI/SW 
Infra to Releng repo has been merged.
*   Patch<https://gerrit.opnfv.org/gerrit/#/c/45083/> making CI/SW 
Infra part of RTD has been under review for quite a long time and will be 
merged once the inclusion of the Pharos docs is excluded from the patch.
  1.  JIRA issues status
 *   INFRA-149<https://jira.opnfv.org/browse/INFRA-149> is still open. We 
need stakeholders around to get update regarding this.
  2.  Octopus project & git repositories
 *   It has been agreed to move SDF to Pharos repo.
 *   Ulrich Kleber<https://wiki.opnfv.org/display/~ulik> has been contacted 
for retirement/archival of Octopus project since noone stepped up to take it 
over.
  3.  Post-Euphrates Jenkins Upgrade
 *   There were no objections to process and 
timeline<https://wiki.opnfv.org/display/INF/Process+and+Timeline+for+Post-Euphrates+Jenkins+Upgrade>
 for the upgrade.
 *   As part of this work, Project-Based Matrix 
Authorization<https://wiki.jenkins.io/display/JENKINS/Matrix+Authorization+Strategy+Plugin>
 Strategy will be enabled.
 *   Additional/different ports might be needed for the slave access from 
different labs. Further discussion is needed.
 *   Jack Morgan<https://wiki.opnfv.org/display/~jmorgan1> will send the 
list of available/unblocked ports to Aric 
Gardner<https://wiki.opnfv.org/display/~admin> for the new Jenkins server.
  4.  Security Release Plan
 *   The draft 
plan<https://wiki.opnfv.org/display/INF/%5BWIP%5D+Security+Release+Plan> has 
been documented by Luke Hinds<https://wiki.opnfv.org/display/~lukehinds> and 
feedback is requested from the community.
 *   It is important to make the checks part of a release Milestone rather 
than having them done just before the release, making things a bit easier to 
fix and track.
 *   We also need to think about how to make none-voting patchset 
verification jobs voting with less disruption.
 *   As part of moving to voting jobs, an intermediate step for projects to 
request exception for certain security issues via a Gerrit keyword which 
removed Verified-1.
 *   Periodic jobs can be looked into as additional feedback channel but 
the question here is how to make the reports available to the projects.
  5.  Zuulv3 Prototype
 *   Very short proposal is put on Etherpad: 
https://etherpad.opnfv.org/p/opnfv-zuul-prototype
 *   TSC will be asked about the budget allocation as we will need few VMs 
to start this prototype.
  6.  Action Items
 *   NEW: Fatih Degirmenci<https://wiki.opnfv.org/display/~fdegir> to add 
topic regarding PDF/IDF/SDF into OPNFV Plugfest/Hackfest agenda.
 *   NEW: Jack Morgan<https://wiki.opnfv.org/display/~jmorgan1> to move PDF 
from Octopus repo to Pharos repo.
 *   NEW: Fatih Degirmenci<https://wiki.opnfv.org/display/~fdegir> and Ray 
Paik<https://wiki.opnfv.org/display/~rpaik> to contact Ulrich 
Kleber<https://wiki.opnfv.org/display/~ulik> regarding the retirement/archival 
of Octopus project.
 *   NEW: Jack Morgan<https://wiki.opnfv.org/display/~jmorgan1> to send 
list of available unblocked ports to Aric 
Gardner<https://wiki.opnfv.org/display/~admin> for new Jenkins server.
 *   NEW: Luke Hinds<https://wiki.opnfv.org/display/~lukehinds> and Fatih 
Degirmenci<https://wiki.opnfv.org/display/~fdegir> to contact David 
McBride<https://wiki.opnfv.org/display/~dmcbride> about having Security as part 
of a release process by adding it to relevant Milestone(s).
 *   NEW: Trevor Bramwell<https://wiki.opnfv.org/display/~bramwelt> to ask 
OPNFV TSC about the Zuulv3 prototype requirements.
 *   NEW: Trevor Bramwell<https://wiki.opnfv.org/display/~bramwelt> and 
Aric Gardner<https://wiki.opnfv.org/display/~admin> to talk about OPNFV Zuulv3 
prototype within LF Infra/Releng to see how it fits into overall LF 
strategy/backlog.
 *   NEW: Jack Morgan<https://wiki.opnfv.org/display/~jmorgan1> and Fatih 
Degirmenci<https://wiki.opnfv.org/display/~fdegir> to re

[opnfv-tech-discuss] [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
RRULE:FREQ=WEEKLY;COUNT=7;INTERVAL=1;BYDAY=MO;WKST=SU
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
SUMMARY;LANGUAGE=en-GB:[Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171113T16
DTEND;TZID=UTC:20171113T17
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104954Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:8
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:8
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171218T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171218T15
DTEND;TZID=UTC:20171218T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104943Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:5
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171225T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171225T15
DTEND;TZID=UTC:20171225T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104943Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:6
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:6
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171211T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171211T15
DTEND;TZID=UTC:20171211T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104939Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:4
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171127T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171127T15
DTEND;TZID=UTC:20171127T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104939Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171204T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171204T15
DTEND;TZID=UTC:20171204T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104939Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] Canceled: [Infra] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Maria Toe
 roe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Christoph
 er Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jose Ange
 l Lausuch:MAILTO:jalaus...@suse.com
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nPlease note the change in start time
  of the meeting\, 16:00 UTC.\n\nThis is to prevent conflicts between Infra
  WG Meeting and OPNFV Plugfest Planning Meeting. (Some) Infra WG Meeting p
 articipants join the plugfest planning call as well.\n\n\n\nThe "Infra Wor
 king Group" plans and tracks infrastructure cross project initiatives.\n\n
 \nWe report our efforts up to the TSC to ensure the community is able to p
 rovide sufficient resources for development and release infrastructure.\n\
 n\n\nTopics and meeting agenda at https://wiki.opnfv.org/display/INF/Infra
 +Working+Group\n\nMinutes at Infra Working Group Meeting<https://wiki.opnf
 v.org/display/meetings/Infra+Working+Group+Meeting>\n\n\n\nWeekly on Monda
 y at 16:00 UTC\n\nGTM Link https://global.gotomeeting.com/join/819733085\n
 \nIRC #opnfv-meeting - freenode.net<http://freenode.net/>\n\n\n\nChaired b
 y Fatih Degirmenci for Nov/Dc (meetings chaired by Infra PTLs on a 2-month
  basis)\n\nYou can also dial in using your phone with Access Code: 819-733
 -085\n\n\n\n   United States +1 (312) 757-3126\n\n   Australia +61 2 8355 
 1040\n\n   Austria +43 7 2088 0034\n\n   Belgium +32 (0) 28 93 7018\n\n   
 Canada +1 (647) 497-9350\n\n   Denmark +45 69 91 88 64\n\n   Finland +358 
 (0) 923 17 0568\n\n   France +33 (0) 170 950 592\n\n   Germany +49 (0) 692
  5736 7211\n\n   Ireland +353 (0) 15 360 728\n\n   Italy +39 0 247 92 13 0
 1\n\n   Netherlands +31 (0) 208 080 219\n\n   New Zealand +64 9 280 6302\n
 \n   Norway +47 75 80 32 07\n\n   Spain +34 911 82 9906\n\n   Sweden +46 (
 0) 853 527 836\n\n   Switzerland +41 (0) 435 0167 13\n\n   United Kingdom 
 +44 (0) 330 221 0086\n\n\n
UID:D22DAC6C-F040-4BBA-8F7A-CFBEFE9B69A6
RECURRENCE-ID;TZID=UTC:20171120T15
SUMMARY;LANGUAGE=en-GB:Canceled: [Infra] Infra Working Group Meeting
DTSTART;TZID=UTC:20171120T15
DTEND;TZID=UTC:20171120T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171110T104938Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-GB:GTM 819733085 and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2115712894
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [infra-wg] [infra][releng] proposal for RELENG project to take ownership of docker build resources

[Fatih Degirmenci]

Hi Yujun,

Thanks for the feedback.

Releng aims to provide a similar service to the OPNFV projects like you 
explained but some of the limitations you listed below are due to Jenkins 
itself and how to manage CI in a consistent manner.
We need to keep some kind of alignment and ensure that what we are doing on 
Jenkins and CI in general fits into the overall framework.

In general, only the Jenkins job configurations and simple wrapper scripts 
should be located in releng repo. (excluding common utilities such as Test 
Result API which will move into a separate repo)
The scripts that do project specific stuff such as running unit tests, builds 
and so on should be owned, developed, and maintained by corresponding projects.

The overall structure followed by releng is like this or from [1].
- preprocessing
- actual build/test
- postprocessing

Preprocessing is simply doing general cleanup stuff, fixing permissions and so 
on before the actual build starts and this is common for all projects.
Postprocessing deals with similar common stuff such as uploading artifacts to 
artifact repo.

The scripts that are consumed by releng from projects are the ones that matter 
and I expect that these change more often than Jenkins jobs or wrappes 
themselves.
Normally you don't need to touch jobs/wrappers if you are not doing a total 
structure change such as changing the job type from Freestyle to Multijob.
These scripts are generally located in /ci/build.sh, 
/ci/test.sh which get executed by the wrapper scripts which in 
turn run by Jenkins jobs.

When it comes to docker; it is a bit different since the use of docker 
containers for the test projects started in releng as common/community 
initiative and the build scripts have been in releng repo developed/maintained 
by the community at large, not just releng itself.
But this is due wanting to have some kind of alignment and historical reasons 
which can be changed if the projects require different way of doing builds and 
so on. (I think Storperf is an example to this.)

We have plans to look into Zuul v3 and start a PoC but we are waiting for 
OpenStack to finalize their migration and fix the issues they are experiencing.
But we also need to keep in mind that we go further in our CI comparing to 
OpenStack so it is not just about OpenStack fixing all the issues but also 
fulfilling OPNFV needs. (one problem we will face is the number/types of 
plugins we use on our Jenkins and the impacts of having long running tests.)

If you can point to specific examples or list additional needs we can take them 
into our backlog and improve what we do.

[1] 
https://wiki.opnfv.org/download/attachments/11699697/image2017-6-6%2022%3A56%3A30.png?version=1=1496783473000=v2

/Fatih

From:  on behalf of "Yujun Zhang (ZTE)" 

Date: Wednesday, 1 November 2017 at 02:19
To: David McBride 
Cc: "infra...@lists.opnfv.org" , test-wg 
, "opnfv-tech-discuss@lists.opnfv.org" 
, Trevor Cooper 
Subject: Re: [infra-wg] [infra][releng] proposal for RELENG project to take 
ownership of docker build resources

Not sure I fully understand the word "ownership" and the scope of building 
resources. For sure it is good to maintain the build scripts and global config 
in releng.

But for project specific configuration, it is not so convenient to manage them 
in a central repository. Sometimes I have to wait for committers of releng to 
merge my patch which just fixes a small bug of the the build job for my 
project. Most time the validation of releng job is only possible after the 
patch is merged. When I found it does not work, I have to go over the steps 
again. It is not so productive since this workflow involves two teams (releng 
and project).

Ideally, I would expect releng to provide the building resource as a service  
and the project specific configuration managed inside project repository. This 
is much like the solution provided by some CI SaaS like Travis-CI[1]. And also 
the trend in OpenStack infra brought in by zuul v3, which is called in repo 
configuration.

This is not just about docker building, but also applies for other verification 
job.

[1]: https://travis-ci.org/
[2]: https://docs.openstack.org/infra/manual/zuulv3.html#what-is-zuul-v3

On Wed, Nov 1, 2017 at 5:56 AM David McBride 
> wrote:
please +1, 0, or -1 to indicate your position

Team,

This topic came up during our release meeting two weeks ago.  I took an action 
to get a discussion started in the infra meeting.

The proposal is for the RELENG project to take ownership of docker build 
resources (scripts,config files, 
etc.)  
for the purpose of providing a common docker build capability 

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] MS11 - tag repos

[Fatih Degirmenci]

Hi,

XCI links are pointing to master versions on purpose so please do not change 
them.

/Fatih

On 25 Oct 2017, at 14:14, Georg Kunz  wrote:

Hi Brandon,
 
Thank you for updating the links. There are a few more links which should be 
updated.
 
Pointing to “latest” documentation instead of stable/euphrates:
VSPERF Test Guide
Barometer Overview
Barometer Release Notes
Barometer User Guide
Doctor Overview
Doctor Release Notes
Doctor User Guide
XCI Overview
XCI Sandbox & User Guide
 
Best regards
Georg
 
From: Brandon Wick [mailto:bw...@linuxfoundation.org] 
Sent: Tuesday, October 24, 2017 3:39 PM
To: Georg Kunz 
Cc: David McBride ; opnfv-project-leads 
; TECH-DISCUSS OPNFV 

Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] 
MS11 - tag repos
 
Thanks Georg, 
 
Agree it makes sense to links to Euphrates docs as much as possible from this 
page. I updated a few links in this regard. Please let us know if you see 
anything else. 
 
Best, 

 
Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org
 
 
On Tue, Oct 24, 2017 at 1:50 AM, Georg Kunz  wrote:
Hi Brandon,
 
I fully agree with Alec and others that the OPNFV tools should be more 
prominently featured and hence, I very much like that the new software download 
page lists those tools as well. Great.
 
One comment though: I noticed that quite a few links on the download page are 
pointing to documentation on the latest (master) branch or to stable/danube. Is 
that intended? Shouldn’t they point to the documentation of the 
stable/Euphrates branch instead?
 
Best regards
Georg
 
 
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Brandon Wick
Sent: Monday, October 23, 2017 4:48 PM
To: David McBride 
Cc: opnfv-project-leads ; TECH-DISCUSS 
OPNFV 
Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] 
MS11 - tag repos
 
Hi Alec, 
 
Thanks for your feedback. The downloads page for Euphrates is being modified to 
include links to testing tools, documentation, dashboards, docker, and XCI. 
Please have a look when it goes live (tonight, 11:00 PM PT), and let us know if 
you have any further recommendations. We can continue to evolve this page over 
time to best fit user needs. 
 
Best, 

 
Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org
 
 
On Mon, Oct 23, 2017 at 7:40 AM, David McBride  
wrote:
+Randy
 
Alec,
 
I think that Randy Levensalor would be a good person to talk with to get an 
end-user perspective.  
 
David
 
 
On Mon, Oct 23, 2017 at 7:29 AM, Alec Hothan (ahothan)  
wrote:
 
The OPNFV release is currently made of a list of installers only (from the link 
you provided me https://www.opnfv.org/software/downloads)
These installers are normally validated by the use of the matching versions of 
OPNFV testing tools. However, the testing tools used to validate that release 
are not available from that download page. Will the euphrates download page 
include containers? It does not look like…
What has been the feedback from consumers of these releases? Did they ask for 
the testing artifacts for each release? Or were they cherry-picking the 
containers directly from dockerhub?
 
We know that some test projects (such as Functest) are already used outside of 
OPNFV labs, and quite possibly on non-OPNFV installers.
 
The TSC should realize there is actually quite a lot of potential interest for 
OPNFV test projects outside of OPNFV environments and there are/will be many 
external users who will be interested in using OPNFV test tools in their own 
environment. So we should consider testing projects as first class citizens – 
at the same level as installers/features.
That is why I have been advocating for an independent versioning for OPNFV test 
projects: make it easier for test project teams to support their artifacts for 
more than 1 consumer (which has been limited to an OPNFV release so far). I 
think this will only strengthen the quality of OPNFV releases.
 
This independent versioning will also provide the right foundation for XCI.
To get to the next level, OPNFV needs to
empower test projects in how they can manage their own releases at their own 
pace
build XCI around this independent versioning model to add more control in the 
current release process
 
Today, there are many hurdles to get to that level. For example, as a project 
PTL, I still cannot build my own container using my project specific tags. All 
I can do 

[opnfv-tech-discuss] Canceled: OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Markos Ch
 andras:MAILTO:mchand...@suse.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Yolanda M
 ota:MAILTO:yrobl...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jack Morg
 an:MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Manuel Bu
 il:MAILTO:mb...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=wutianwei
 :MAILTO:wutianw...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Nikolas H
 ermanns:MAILTO:nikolas.herma...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=BLAISONNE
 AU RD-CORE-LAN:MAILTO:david.blaisonn...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=mardim@in
 tracom-telecom.com:MAILTO:mar...@intracom-telecom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Bob Monk
 man':MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=zhang.jun
 3...@zte.com.cn:MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=fangfang 
 (C):MAILTO:fangfa...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Periyasam
 y Palanisamy:MAILTO:periyasamy.palanis...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Stephen W
 ong:MAILTO:stephen.wo...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=tapio.tal
 lg...@nokia.com:MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Dave Ursc
 hatz:MAILTO:dave.ursch...@cengn.ca
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=taseer94@
 gmail.com:MAILTO:tasee...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\nWe need to cancel this week's meeting. T
 alk to you all next week!\n\n/Fatih\n\n\n\nHi\,\n\nWelcome to OPNFV Cross 
 Community CI (XCI) Meeting!\n\nYou can see the agenda for the upcoming mee
 ting on https://etherpad.opnfv.org/p/xci-meetings\n\nPlease note that this
  is an IRC-only meeting on #opnfv-pharos channel held on a weekly basis.\n
 Please let me know in case if you want to have meeting with voice/screen s
 haring to discuss/demo things in advance so I can fix GTM for that meeting
 .\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageId
 =8687635\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20XCI
 /\n\n/Fatih\n
UID:580EB2B8-73C8-440B-9F2D-6CF66601334A
RECURRENCE-ID;TZID=W. Europe Standard Time:20171025T15
SUMMARY;LANGUAGE=en-GB:Canceled: OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20171025T15
DTEND;TZID=W. Europe Standard Time:20171025T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171024T202133Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2115460920
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
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][ovsnfv] Disabling RPM builds in ovsnfv

[Fatih Degirmenci]

Hi Thomas,

The change below disables daily jobs. If you think you will never need these 
jobs, we can remove them completely.

https://gerrit.opnfv.org/gerrit/#/c/45181/

A related question; are packages for debian built somewhere?

/Fatih

From:  on behalf of Thomas F 
Herbert 
Date: Sunday, 15 October 2017 at 16:55
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [releng][ovsnfv] Disabling RPM builds in ovsnfv


Question about best way to disable RPM builds in ovsnfv

In the August ovsnfv meeting we agreed to disable the building of OVS and DPDK 
RPM artifacts within the ovsnfv project as this effort is redundant with OVS 
RPMs found in downstream Centos repos.

Having received no negative public comments,  we merged a local patch to ovsnfv.

However, we are still getting build errors in Euphrates daily builds: 
https://build.opnfv.org/ci/job/ovsnfv-daily-euphrates/11/console

Do we need to cherry-pick that patch to a different patch or should the disable 
of ovsnfv builds be done with a patch releng?

--Tom
--
Thomas F Herbert
NFV and Fast Data Planes
Office of Technology
Red Hat
___
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] Alpine for arch

[Fatih Degirmenci]

Hi Cedric,

I see lots of conversations around how to build stuff, test them, apply tags 
but it is very hard to follow things. Things are going too fast and with little 
explanation. Each and every new thing coming up will make it harder for us to 
understand what you need.

Also the builds first pushed to docker hub then travis ci now. I am not sure 
about this either. I suppose you will try all the external ci services instead 
of telling us what you need clearly...

So, before I say if something is possible or not, you need to come up with 
clear requirements. We can then fix whatever you need together with you.

/Fatih

On 14 Oct 2017, at 12:32, Cedric OLLIVIER  wrote:

Hello,

We simply require concurrent jobs properties which can be simplified
here as parallel builds, concurrency control and dependency.
They are mainly required as:
 - functest-core must be built before other Functest containers
 - other containers should be built in parallel as soon as
functest-core is published
 - amd64 containers and arm64 containers should be built in parallel

I am not directly involved in Releng and I have read in reviews or
mails that today's jjobs don't support that.
All proposals to build Alpine containers haven't conformed with the
concurrency control and the dependencies.
@Fatih could you please confirm that? I'm quite sure that Jenkins supports them.

In case of cross building arm64 images on amd64 PODs, we also require
several operations on PODs:
 - to install qemu-user-static
 - to support binfmt-misc [1]

The current Docker Automated builds had been fine before we were asked
to build Alpine arm64 images and to publish stable tags:
- arm64 images can't be built via this CI tool as it requires
qemu-user-static and binfmt_misc [1] support on Docker hosts.
- publishing stable tags triggers useless builds simply because they
are already triggered by euphrates tags.

I'm currently beta testing travis-ci to meet all requirements:
- https://travis-ci.org/collivier/functest/builds/287849046 (stable/euphrates)
- https://travis-ci.org/collivier/functest/builds/287745681 (master)

It works very well and all scripts are ran in parallel for all steps:
- build functest-core images
- publish functest-core manifests
- build all functest images
- publish all manifests

I am considering we do switch from Docker Automated builds to
travis-ci for official Functest images if releng jjobs are not
updated.
But I think it's too late regarding the deadline for E as we should
multiply CI runs. @David, do you agree?
(Of course I am not allowed to configure travis-ci for OPNFV github
repositories).

I will deeply update the wiki page "Docker Requirements on Releng" [2]

[1] https://www.kernel.org/doc/html/v4.11/admin-guide/binfmt-misc.html
[2] https://wiki.opnfv.org/display/functest/Docker+Requirements+on+Releng

Cédric

2017-10-11 9:56 GMT+02:00 Jose Lausuch :
> Maybe late for 5.0, but not late for Euphrates 5.1.
> 
> Can we collect a list the requirements we need from Releng in this wiki [1]?
> It will facilitate the support and I will help to speed it up. Otherwise,
> nothing will happen as people don’t know what we need.
> 
> [1] https://wiki.opnfv.org/display/functest/Docker+Requirements+on+Releng
> 
> 
> 
> 
> 
> 
> On 11 Oct 2017, at 09:42, Cristina Pauna  wrote:
> 
> Hi Cedric,
> 
> Which E are you refering to in this email? The one with deadline on 15th
> December?
> 
> Cristina
> 
> From: cedric.olliv...@orange.com [mailto:cedric.olliv...@orange.com]
> Sent: Wednesday, October 11, 2017 7:24 AM
> To: RICHOMME Morgan IMT/OLN ;
> jalaus...@suse.com; Delia Popescu ; Alexandru
> Avadanii ; Cristina Pauna
> ; wangwu...@huawei.com
> Cc: opnfv-tech-discuss 
> Subject: Re: [functest] Alpine for arch
> 
> 
> Hello,
> 
> I quickly tested to build aarch64 Functest images via Docker automated
> builds what is impossible (several prerequisites are unmet). I precise the
> first published images were built locally.
> 
> I'm thinking about an alternative way which will be too much disruptive for
> E release. Again it will be suitable for my own repositories. But releng
> should have been the target to build all Docker images (I bet it won't be
> ready for E). Today's releng can't meet functest prerequisites about Docker.
> 
> I will inform as soon as my own repositories are ready.
> 
> Cédric
> 
>  Cristina Pauna a écrit 
> 
> Hi,
> 
> There has been a lot of confusion and changes around this topic and I want
> to clear things up going forward, so we do not waste any of our time.
> What I understand from all the disparate discussions around this topic is:
> 1.   We will not do alpine for E0 release on arm, we are targeting E1/E2
> 2.   For the Functest-core image we will have 1 Dockerfile for x86, and
> a patch 

Re: [opnfv-tech-discuss] [VSPERF][NFVBENCH] streamlining the jump host to data plane wiring

[Fatih Degirmenci]

Hi,

I think there is a misunderstanding, especially with this: "The first hurdle is 
that all test containers run inside a VM on the jump host today."

I would like to clarify this and add some more details.

Test containers do not run inside a VM on the jump host today. Test containers 
directly run on the jumphost.

What I was referring to you when we had chat is the initiative Infra WG has 
been driving to move installers into VMs on jumphosts so the installation 
process can be isolated from the jumphost and driven from a VM in order to 
ensure installers can use any PODs we have.

The reason for this is that we currently use dedicated PODs per installer and 
these installers directly run on jumphosts, depending on OS and some other 
stuff on jumphosts (I have suspicions that they even expect certain usernames 
for the login user which is really strange).
This really makes things difficult for us in Infra, for the developers, and for 
the end users since noone knows what we have on those jumphosts and the state 
of CI POD jumphosts is a big question. (some jumphosts haven't been 
cleaned/reinstalled for 2 about years.)
This is not really a good practice since we basically do not have any change 
control on these machines and whatever is done there has possibility to cause 
headaches. (for example, strange failures which you can't reproduce elsewhere.)
And finally, our releases come out from these PODs so it is another big 
question; reproducibility of entire release...

We haven't been able to get the above idea implemented by installers and this 
results in other issues such as resource shortage and so on which is nothing 
compared to issues listed above.

As part of XCI initiative, we aim to apply all the ideas brought up by Infra WG 
over time and demostrate the benefits of what we have been proposing. 
(dogfooding)
This is not limited to having a VM on jumphost where the installation process 
is driven.
All the PDF, SDF, VM, dynamic CI, CI evolution etc. activities actually pursue 
to ensure we can have full traceability, reproducibility (CM101), and we use 
our resources wisely, shortening the time it takes for us to do things rather 
than things waiting in the queue for days. (Long list shows that none of the 
ideas we brought up was actually implemented which should be another concern 
for the community and a topic to brought up to TSC.)

One of the first things XCI Team started working on is putting the components 
used by XCI into a VM on jumphost so we always get the same behavior by the use 
of a clean machine and we can use any and every POD OPNFV has.
We also support 3 distros; Ubuntu, Centos, OpenSUSE. So we are basically 
independent from whatever POD we might be run on. PDF is the other and 
important part of what we are doing so we can have total independence from PODs.
SDF will put the missing piece to get the BOM for any and every deployment and 
testing that is done in XCI.

Putting test containers into VM and running testing from there have been part 
of our overall strategy.

However, after talking with Alec on IRC, it was clear that putting test 
containers to VM is not applicable to all the testing projects.
As summarized above, the reason for us to use VMs is to isolate things from the 
physical jumphost  and ensure everything starts clean for reproducibility and 
so on.
Using containers for test projects serve the same purpose; isolation and 
reproducibility so we do not see any issue here and will do our best to support 
you, ensuring you get what you need as long as it fits into the overall 
strategy set by Infra WG.
If we find something that doesn't fit, we can bring that topic to Infra WG and 
can do necessary adjustments if possible.

/Fatih

From: "Alec Hothan (ahothan)" <ahot...@cisco.com>
Date: Friday, 29 September 2017 at 18:22
To: Wenjing Chu <wenjing@huawei.com>, Trevor Cooper 
<trevor.coo...@intel.com>, "opnfv-tech-discuss@lists.opnfv.org" 
<opnfv-tech-discuss@lists.opnfv.org>
Cc: Fatih Degirmenci <fatih.degirme...@ericsson.com>, Jack Morgan 
<jack.mor...@intel.com>
Subject: Re: [opnfv-tech-discuss] [VSPERF][NFVBENCH] streamlining the jump host 
to data plane wiring


I had an irc chat with Fatih and went through the various hurdles. The first 
hurdle is that all test containers run inside a VM on the jump host today. That 
is not going to work well with software traffic gen as they require direct 
access to the NIC using DPDK (well technically you can run a traffic gen in a 
VM but I think we need to run them native or container native to get the best 
performance and best clock accuracy).

So we will need to allow some test containers to run native on the jump host, 
which is not a problem per se, just need to coordinate with XCI team to support 
that mode.
Second hurdle is to standardize how every jump host should be tied to the pod 
data plane: specify NIC card, wiring requirements and

[opnfv-tech-discuss] XCI Meeting Minutes - September 27th

[Fatih Degirmenci]

Hi,

Meeting minutes are available on 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-09-27-13.00.txt
 
/Fatih

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

[opnfv-tech-discuss] XCI Meeting Minutes - September 20th

[Fatih Degirmenci]

Hi,

Meeting minutes are available on 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-09-20-13.00.txt
 
/Fatih

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

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Markos Ch
 andras:MAILTO:mchand...@suse.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Yolanda M
 ota:MAILTO:yrobl...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jack Morg
 an:MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Manuel Bu
 il:MAILTO:mb...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=wutianwei
 :MAILTO:wutianw...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Nikolas H
 ermanns:MAILTO:nikolas.herma...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=BLAISONNE
 AU RD-CORE-LAN:MAILTO:david.blaisonn...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=mardim@in
 tracom-telecom.com:MAILTO:mar...@intracom-telecom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Bob Monk
 man':MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=zhang.jun
 3...@zte.com.cn:MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=fangfang 
 (C):MAILTO:fangfa...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Periyasam
 y Palanisamy:MAILTO:periyasamy.palanis...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Stephen W
 ong:MAILTO:stephen.wo...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=tapio.tal
 lg...@nokia.com:MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Dave Ursc
 hatz:MAILTO:dave.ursch...@cengn.ca
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=taseer94@
 gmail.com:MAILTO:tasee...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nYou can see the agenda for the upcoming meeting on h
 ttps://etherpad.opnfv.org/p/xci-meetings\n\n\n\nPlease note that this is a
 n IRC-only meeting on #opnfv-pharos channel held on a weekly basis.\n\nPle
 ase let me know in case if you want to have meeting with voice/screen shar
 ing to discuss/demo things in advance so I can fix GTM for that meeting.\n
 \n\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pageI
 d=8687635\n\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV%20
 XCI/\n\n\n\n/Fatih\n
RRULE:FREQ=WEEKLY;UNTIL=20171220T14Z;INTERVAL=1;BYDAY=WE;WKST=SU
UID:580EB2B8-73C8-440B-9F2D-6CF66601334A
SUMMARY;LANGUAGE=en-GB:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20170920T15
DTEND;TZID=W. Europe Standard Time:20170920T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170919T113717Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2115460920
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
X-MICROSOFT-LOCATIONDISPLAYNAME:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-LOCATIONSOURCE:None
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [release][euphrates] stable branch window

[Fatih Degirmenci]

Hi,

Releng will not have a stable/euphrates branch.

The plan was to move none-jjb stuff out of releng and releng-utils was 
identified as the new repo for modules. This repo can then follow usual 
branching like the rest of the OPNFV projects. [1]

Adding Trevor to see where we are wih the move.

[1] https://wiki.opnfv.org/display/INF/Split+up+Releng+Repository
 
/Fatih

On 2017-09-10, 22:50, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
Cedric OLLIVIER"  wrote:

Hello,

Could you please confirm that no stable/euphrates branch will be
created for releng again?
Else we are obliged to select a specific git commit id to build our
Functest stable containers which is not the best way.
I precise Functest depends on the opnfv python package which is hosted
by releng (https://git.opnfv.org/releng/tree/modules).

Cédric

2017-09-09 1:24 GMT+02:00 David McBride :
> Reminder...
>
> The stable branch window closes as of MS7, one week from today, on 
September
> 15 at 12 p.m. (PT). PTLs - please contact Aric as soon as you're ready to
> branch.  Aric will branch any projects that have not already been branched
> on Sept 15.
>
> Let me know if you have any questions.
>
> David
>
> On Tue, Aug 29, 2017 at 3:23 PM, David McBride
>  wrote:
>>
>> Team,
>>
>> As you know, MS6 was this past Friday, Aug 25.  In addition to the
>> requirements associated with MS6, this milestone also marks the opening 
of
>> the stable branch window, which subsequently ends with MS7 on Sept 15.
>>
>> This means that PTLs may request to branch their project any time before
>> Sept 15.  Note that I erroneously told the release meeting this morning 
that
>> PTLs may create their own branch.  That's not the case.  Instead, please
>> contact Aric (copied) and request that he create the branch for you.
>>
>> Also, as a reminder, we have changed the version number format as of the
>> Euphrates release.
>>
>> 5.0.0 - Euphrates initial release version
>> 5.1.0 - Euphrates SR1
>> 5.2.0 - Euphrates SR2
>>
>> Let me know if you have any questions.
>>
>> David
>>
>> --
>> David McBride
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>
>
>
>
> --
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>
> ___
> 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] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Fatih Degirmenci]

Thanks Markos & Yolanda.

Ray,

I accept the nomination.

/Fatih

From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Raymond Paik 
<rp...@linuxfoundation.org>
Date: Wednesday, 6 September 2017 at 17:36
To: Yolanda Mota <yrobl...@redhat.com>
Cc: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>, 
"opnfv-...@lists.opnfv.org" <opnfv-...@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations 
for Committers-at-Large TSC & Committer Board elections

Markos/Yolanda:

Thanks for kicking things off.

Fatih, I assume you accept the nomination?

Thanks,

Ray

On Wed, Sep 6, 2017 at 2:30 AM, Yolanda Robla Mota 
<yrobl...@redhat.com<mailto:yrobl...@redhat.com>> wrote:
I fully support that, Fatih has done an incredible job with XCI, promoting the 
job and making it known in OPNFV and in other communities.

On Wed, Sep 6, 2017 at 10:47 AM, Markos Chandras 
<mchand...@suse.de<mailto:mchand...@suse.de>> wrote:
On 09/05/2017 05:31 AM, Raymond Paik wrote:
> [...]
> Nominations should be posted to opnfv-tech-discuss & opnfv-tsc
> mailing lists by 5pm Pacific Time on September 8th (Friday).  You
> are welcome to reply to this email or if you're sending out a
> separate note, please include phrases like "Committer Board
> nomination" or "Committer-at-Large TSC nomination" in email
> subjects.  In nomination statements, please list the following
> information:
>
>   * Which election (TSC vs. Board) the nomination is for
>   * Name of the nominee
>   * Organization
>   * A brief description of nominee's qualifications
> [...]

I would like to nominate Fatih Degirmenci (Ericsson) for the TSC
election. He has done a great work leading, planning, designing and
improving the XCI project and he also understands the inter-project
requirements across the OPNFV spectrum which I believe is an valuable
skill for a TSC member.

--
markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

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


--

Yolanda Robla Mota

Principal Software Engineer, RHCE

Red Hat

<https://www.redhat.com>

C/Avellana 213

Urb Portugal

yrobl...@redhat.com<mailto:yrobl...@redhat.com>M: 
+34605641639<http://redhatemailsignature-marketing.itos.redhat.com/>
[mage removed by sender.]<https://red.ht/sig>

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto: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] Proposal for CD Oriented Release Model

[Fatih Degirmenci]

Hi,

The proposal for CD-oriented release model is available on the page linked 
below. This topic is scheduled for the Weekly Technical Community Discussion on 
Thursday.

https://wiki.opnfv.org/display/INF/Release+Process+Proposal

We also documented the information regarding how to onboard projects and 
scenarios to XCI. 
Please note that the information on this page is preliminary and subject to 
change based on the learnings from SFC and discussions within the community.

https://wiki.opnfv.org/pages/viewpage.action?pageId=12390152
 
/Fatih



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

[opnfv-tech-discuss] XCI Meeting Minutes - August 30th

[Fatih Degirmenci]

Hi,

Meeting minutes are available on 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-08-30-13.00.txt
 
/Fatih

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

Re: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

[Fatih Degirmenci]

Hi,

About using docker hub for builds; I thought the docker builds would remain on 
OPNFV Jenkins due to the limitation you highlighted below and the other 
limitations/potential issues we summarized in earlier discussions. [1]
I might have missed to followup discussions that have happened during the 
summer period so I'd be happy to catch up and read the reasons behind this.

If you still think of moving to docker hub for builds, we need to think and 
have a long term strategy rather than just moving builds to there and getting 
paid service as it will limit our ability to improve how we are doing things 
for test projects or projects that are building docker images.

[1] https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.html
 
/Fatih

On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
morgan.richo...@orange.com"  wrote:

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV 
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.

Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?

Any comment welcome

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and 
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
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] [infra-wg] Following-up on the Jira-sync discussion at the Infra WG mtg.

[Fatih Degirmenci]

Hi,

First of all, apologies for late response to this as I've been out for a
while.

As I mentioned during the TSC call last week, what I see on the proposal is
that it

- mainly focuses on technical aspects of the proposed sync solution by
creation of a new project for LF RE Team on OPNFV Jira and enabling the
sync of this project to LF Jira
- skips the details of what type of issues should be logged to this new
project
- has possibility to create confusion while creating tickets
- ignores the established way of working with Infra Jira project

Here is the list of places and type of issues that are logged/tracked on
them.

- OPNFV Helpdesk: General LF IT related issues that are handled by LF RE
Team. (Jenkins, slaves, artifact repository, gerrit/git, etc.)
- Infra project on OPNFV Jira: None-project related requests to OPNFV Infra
- Releng project on OPNFV Jira: Releng project work.
- Pharos project on OPNFV Jira: Pharos project work.

Here are the questions/concerns/comments,

- As highlighted above, it is unclear what type of issues are expected to
be logged to the newly proposed project on Jira.
- Will this new proposed solution replace Helpdesk when it comes to
Jenkins, slaves, artifact repository etc. that are currently handled by LF
RE Team by sending mails to OPNFV Helpdesk?
- OPNFV Infra WG continuously works with OPNFV Infra Jira project and
assigns issues to the right people, asks status to ticket
creators/assignees to keep the status of the tickets up to date as it is
nearly impossible for everyone to know who the issue should be assigned to.
Rather than adding yet another project and asking community to try to
guess/pick one of the 5 places to log the issue, keeping the established
way of working might be more practical and less confusing.

Just to make it clear that we have been asking for more visibility to the
tickets community submits to helpdesk for nearly 2 years so I fully support
the initiative to make things more visible but only if the responsibilities
are clearly defined (as the LF RE team members are also project committers
and some of the items in LF RE backlog overlaps with OPNFV Releng project
work) and the community is informed with the possible impacts to the
current way of working.

/Fatih




On 28 July 2017 at 07:01, Raymond Paik  wrote:

> All,
>
> For those of you who attended the Infra WG call on the 24th, you'll
> remember that we weren't able to do the Jira sync demo due to GTM issues.
> Andy recorded the demo and you can find this under the agenda item from the
> 24th in the Infra WG meetings page
>  (see "Jira sync
> proposals").  Demo links can be found on slide 6 & 8.
>
> Please take a look and let me/Andy/Brandy know if you have any questions
> or feedback.
>
> Thanks,
>
> Ray
>
> ___
> infra-wg mailing list
> infra...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/infra-wg
>
>
___
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] docker build fails

[Fatih Degirmenci]

Hi,

This machine has been removed from build server pool on Jenkins while we 
troubleshoot it.
It will be added back once it is back to normal.

/Fatih

From:  on behalf of "Yujun Zhang 
(ZTE)" 
Date: Monday, 28 August 2017 at 04:33
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] [releng] docker build fails

Hi releng,

It seems the docker build service is not available. Is there anybody who can 
have a look?

Something seems wrong with the docker daemon on the server[1]:


[qtip-docker-build-push-master] $ /bin/bash /tmp/hudson2319564546050375447.sh

Starting opnfv-docker for opnfv/qtip ...





Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the 
docker daemon running?

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the 
docker daemon running?

Current branch: master

Building docker image: opnfv/qtip:latest





docker build --no-cache -t opnfv/qtip:latest --build-arg BRANCH=master -f 
Dockerfile .

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the 
docker daemon running?


[1]: 
https://build.opnfv.org/ci/view/docker/job/qtip-docker-build-push-master/416/console


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

Re: [opnfv-tech-discuss] Delays due to Intel outage

[Fatih Degirmenci]

Hi,

I closed the ticket now. Thanks to all for quickly fixing the issue.

/Fatih

From:  on behalf of "Beierl, Mark" 

Date: Wednesday, 23 August 2017 at 15:41
To: Manuel Buil 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: Re: [opnfv-tech-discuss] Delays due to Intel outage

It looks to be resolved now, although the ticket remains open.  Thanks to the 
team that restored the connectivity!

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Aug 22, 2017, at 16:29, Manuel Buil > 
wrote:

Hello David, Mark,

Thanks for bringing this up Mark. SFC is also impacted by this outage :(

Regards,
Manuel

On Tue, 2017-08-22 at 19:59 +, Beierl, Mark wrote:
Hello, David.

I am sending this as a heads up.  There has been an outage in Intel [1] since 
yesterday and it is causing a minor impact to StorPerf as we have been without 
our primary development and CI pod since it started.  Right now, I don't 
anticipate any problems with the next milestone for StorPerf.

If this lasts much longer, there may be other projects that are impacted too.

[1] https://jira.opnfv.org/projects/INFRA/issues/INFRA-161

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
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

[opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

[Fatih Degirmenci]

Hi,

Please see the proposal regarding the number of servers and hardware specs for 
LaaS from the links below.

·   Number of x86 and ARM servers: 
https://wiki.opnfv.org/display/INF/Lab+as+a+Service#LabasaService-LaaS-NumberofServers
·   Definition of hardware for x86 and ARM: 
https://wiki.opnfv.org/display/INF/Lab+as+a+Service#LabasaService-LaaSHardware

Please share your thoughts, comments and questions either by replying to this 
mail, directly on Wiki page, or by joining the Infra WG Meeting on August 21st 
where this topic will be discussed.
 
/Fatih

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

Re: [opnfv-tech-discuss] OPNFV Docker builds on Dockerhub account

[Fatih Degirmenci]

Hi,

It looks nice!

Here are some comments.

The most important comment I have is the ability to run docker builds for 
patches as part of verify jobs and post feedback to OPNFV Gerrit. If we go this 
path, we will have pre-merge builds done on our machines and post-merge builds 
done on docker hub, which will result in at least same amount of maintenance 
effort if not more. Also things might result differently due to having 2 
different environments where the builds are done.

The other comments are the synching, the no of concurrent builds, and the 
visibility.

The synching will definitely slow things down as we need to wait for it to be 
done. This might be annoying when a crucial bugfix needs to be merged/built. 
The other possibility is if/when we have issues with synching which might 
further delay builds.

The no of concurrent builds will cause limitations time to time and some builds 
will have to wait in the dockerhub queue.

And finally there will be 2 places to look at for the builds/logs for different 
things; OPNFV jenkins and docker hub.

Also, the synching and concurrent build limit will contribute to the increase 
in time to get feedback as well. Time to get feedback will increase to time to 
synch + possible queueing from direct/post-merge triggered builds on our 
Jenkins.

Ps. I will be one of the happy persons if we move to docker hub so I can get 
rid of maintaining build servers. But I also need to highlight some of the 
limitations if we do this.

/Fatih

On 19 Jul 2017, at 15:30, Jose Lausuch  wrote:

Hi,
 
Following up on the discussion about how to build our Docker images, I started 
a trial with Trevor Bramwell with automated builds on Dockerhub for some of the 
new Functest Docker images:
https://hub.docker.com/r/opnfv/functest-core/builds/
https://hub.docker.com/r/opnfv/functest-smoke/builds/
https://hub.docker.com/r/opnfv/functest-healthcheck/builds/
 
It triggers a build after the corresponding repository in Github (mirror) has 
new code. Basically, whenever a new patch is merged on OPNFV gerrit and synched 
with Github.
 
There is currently a small limitation in the OPNFV Dockerhub account: it can 
build only 1 image at a time, but we can change that up to 5 or more parallel 
builds by requesting an account upgrade to LF. You can see the pricing plan 
here:
https://hub.docker.com/account/billing-plans/
 
We could use this to avoid load on our build servers, use them for something 
else and of course stop maintaining docker builds in OPNFV.
I would like to know your opinion on that.
 
Thanks,
Jose
 
___
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] Lab as a Service - Installer Support

[Fatih Degirmenci]

Hi QiLiang,

Please take a look at below table for some of the use cases.

https://wiki.opnfv.org/display/INF/Lab+as+a+Service#LabasaService-OPNFVLaaSinitialuse-cases

Apart from that, the intention with LaaS to create PODs on the fly meaning that 
the resources will be pooled and assigned to
- standalone machines for virtual deployments
- pharos PODs for baremetal deployments
- pharos POD + additional node(s) for other purposes such such as OPNFV + MANO

depending on the request so we can build up and tear down resources dynamically.

The starting point is virtual deployments to prototype the idea which can/will 
be done on the machines hosted by UNH.

/Fatih

On 18 Jul 2017, at 09:51, liangqi (D)  wrote:

Hi Lincoln,
 
Got it, thanks. So the users can get a pod with user specific opnfv scenario 
installed, or a pod with user specific OS-only installed.
 
BTW, I'm curious about how do the labaas's pods managed. Do the scripts 
opensourced, can I get the code?
 
Regards,
QiLiang
From: Lincoln Lavoie [lylav...@iol.unh.edu]
Sent: Tuesday, July 18, 2017 0:42
To: liangqi (D)
Cc: Luke Hinds; opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] Lab as a Service - Installer Support

Hi QiLiang,

Some answer inline below, at least for how we've set stuff up so far.



> On Mon, Jul 17, 2017 at 11:56 AM, liangqi (D)  wrote:
> I can give some support from compass side. Also I'm recently working on opnfv 
> installers' quickstart wrapper scripts( 
> https://gerrit.opnfv.org/gerrit/#/c/36711/ ). Hope the scipts could ease 
> developers/users better use the labaas resources.
>  
> Here are three questions, after checked the wiki page:
> - How do the Laas resources allocated? Allocated as vpods pool and BM(1+3+2) 
> pods pool? 
We have systems setup to allow two virtual pods per hardware node to run in the 
lab.  This is based on RAM/Disk/etc.  Access to a pod resource would be 
scheduled through the Pharos dashboard system.
 
> - How do the vpods' and BM jumpserver's operating systems installed, manually 
> pre installed by lab admin or auto installed trigger by jenkins when the pod 
> is allocated?
We've built up some scripts and support to allow the virtual pod to be "spun 
up" by the request through the dashboard.  This isn't actually hooked up to 
Jenkins, if I understand it correctly, it's its own thing.  We are trying to 
keep the system admin out of the request path.  This does depend on the 
installer supporting a virtual deployment and a "hands off" deployment approach.

This will likely start with basic requests, i.e. one 1 or 2 scenarios supported 
and go out from there.  We're also planning a developer version, where the 
actual OPNFV deployment doesn't occur, so the developer can login and pull 
their own artifacts onto the system to deploy from, etc.  Because the systems 
are self contained and "throw away."  We'll be able to give root access onto 
the environment for each Pod User.  At the end of the Pod's lifetime, it just 
gets deleted.
 
> - Do laas pods share the same jenkins master with other opnfv pods or the 
> laas will host a jenkins master to manage all the laas resources?
No, see above.
 
>  
> Regards,
> QiLiang
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Luke Hinds 
> [lhi...@redhat.com]
> Sent: Monday, July 17, 2017 22:39
> To: opnfv-tech-discuss
> Subject: [opnfv-tech-discuss] Lab as a Service - Installer Support
> 
> Dear Installer Projects,
> 
> I have an action from the infra-wg to gauge which installers can support LaaS.
> 
> Please peruse the following wiki link for more details on the effort.
> 
> https://wiki.opnfv.org/display/INF/Lab+as+a+Service
> 
> Recommend you go over the work flow in detail, and consider if you have 
> interfaces that can accept the requests and process deployment status.
> 
> Any question, please ask over this email or attend the infra-wg group.
> 
> Many Thanks,
> 
> 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
> 



-- 
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies


www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[Fatih Degirmenci]

+1 to "Can we work on a proposal and get every project that deals with 
containers involved?"

It is mainly test projects who use containers so I again let testing community 
to take the lead and point you to where/how the conversation started.

We can then try to generalize it later on.

/Fatih

On 11 Jul 2017, at 17:16, Alec Hothan (ahothan)  wrote:

Can we work on a proposal and get every project that deals with containers 
involved?
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Cross Community CI (XCI) Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Markos Ch
 andras:MAILTO:mchand...@suse.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Yolanda M
 ota:MAILTO:yrobl...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Jack Morg
 an:MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Juan Vida
 l ALLENDE:MAILTO:juan.vidal.alle...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Manuel Bu
 il:MAILTO:mb...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=wutianwei
 :MAILTO:wutianw...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Nikolas H
 ermanns:MAILTO:nikolas.herma...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=BLAISONNE
 AU RD-CORE-LAN:MAILTO:david.blaisonn...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=mardim@in
 tracom-telecom.com:MAILTO:mar...@intracom-telecom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Bob Monk
 man':MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=zhang.jun
 3...@zte.com.cn:MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=fangfang 
 (C):MAILTO:fangfa...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:Hi\,\n\n\n\nWelcome to OPNFV Cross Community CI 
 (XCI) Meeting!\n\n\n\nYou can see the agenda for the upcoming meeting on h
 ttps://etherpad.opnfv.org/p/xci-meetings\n\n\n\nPlease note that this is a
 n IRC-only meeting on #opnfv-pharos channel held on a bi-weekly basis.\n\n
 Please let me know in case if you want to have meeting with voice/screen s
 haring to discuss/demo things in advance so I can fix GTM for that meeting
 .\n\n\n\nXCI @ OPNFV Wiki: https://wiki.opnfv.org/pages/viewpage.action?pa
 geId=8687635\n\nXCI @ OPNFV Jenkins: https://build.opnfv.org/ci/view/OPNFV
 %20XCI/\n\n\n\n/Fatih\n
RRULE:FREQ=WEEKLY;UNTIL=20171018T13Z;INTERVAL=2;BYDAY=WE;WKST=SU
UID:580EB2B8-73C8-440B-9F2D-6CF66601334A
SUMMARY;LANGUAGE=en-GB:OPNFV Cross Community CI (XCI) Meeting
DTSTART;TZID=W. Europe Standard Time:20170719T15
DTEND;TZID=W. Europe Standard Time:20170719T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170711T143550Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-GB:IRC-only (#opnfv-pharos on freenode)
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115460920
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[Fatih Degirmenci]

Hi Alec,

Your understanding about the docker image tags seem correct to me (latest vs 
stable) but I let someone from test projects answer to that.

When it comes to artifact versioning in general; you are asking really good 
questions. Let me go back in time and summarize what plans we had (ie what we 
haven't been able to implement fully) with regards to it.

The questions you ask about tagging docker images is not limited to them. We 
have similar issues with other artifacts we produce (rpms, isos , etc.), maybe 
not on the same level as the docker images but we have them.
In order to achieve some level of traceability and reproducibility, we record 
the metadata for the artifacts (rpms, isos, etc.) we build so we can go back to 
source and find out exact version (commit) that was used for building the 
artifact in question. [1]
We also had plans to tag corresponding commits in our git repos but we haven't 
managed to fix that. [2] This includes docker images as well.

Apart from our own (OPNFV) repos, some of the artifacts we build include stuff 
from other sources, making it tricky to achieve full traceability and making 
the traceability even more important.
We had many discussions about how to capture this information in order to 
ensure we can go back to a specific commit in any upstream project we consume. 
(locking/pinning versions etc.)
But since we have different ways of doing things and different practices 
employed by different projects, this hasn't happened either. (I can talk about 
this for hours...)

By the way, I am not saying we totally failed as some projects take care of 
this themselves but as OPNFV, we do not have common practice, except metadata 
files for ISOs and the docker tags that do not help at all.

Long story short, this can be achieved in different ways like you exemplified; 
if a tag is applied to a repo, we trigger a build automatically and store & tag 
produced artifact in artifact repo and/or if we are building periodically, we 
apply the tag to git repo once the artifact is built successfully.

No matter which way we go, we need to fix this so thank you for questioning 
things, hopefully resulting in improvements starting with test projects.

[1] http://artifacts.opnfv.org/apex/opnfv-2017-07-05.properties
[2] https://jira.opnfv.org/browse/RELENG-77

/Fatih

From: "Alec Hothan (ahothan)" <ahot...@cisco.com>
Date: Monday, 10 July 2017 at 21:45
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>, "Beierl, Mark" 
<mark.bei...@dell.com>
Cc: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org>, 
"test...@lists.opnfv.org" <test...@lists.opnfv.org>
Subject: [test-wg] docker container versioning


[ cc test-wg - was [opnfv-tech-discuss] Multiple docker containers from one 
project) ]


Hi Fatih

It is generally not easy to deal with container tags that do not include any 
information that links easily to a git repo commit (e.g. a “version” number 
increased by 1 for each build does not tell which git commit was used – might 
be one reason why this was removed)

For example, if we look at the published yardstick containers as of today:

“latest” is generally used to refer to the latest on master at the time of the 
build (so whoever does not care about the exact version and just wants the 
bleeding edge will pick “latest”) – apparently this container is not linked to 
any particular OPNFV release? Or is it implicitly linked to the current latest 
release (Euphrates)?

“stable” is supposed to be the latest stable version (presumably more stable 
than latest), in the current script it is not clear in what conditions a build 
is triggered with BRANCH not master and RELEASE_VERSION is not set (does the 
project owner controls that?) Apparently unrelated to any particular OPNFV 
release as well although would have thought a “danube.3.0-stable” would make 
sense.

“danube.3.0”: related to Danube 3.0 but does not indicate what yardstick repo 
tag it was built from. The git repo has a git tag with the same name 
“danube.3.0”, how are those 2 tags correlated? For example, there is no 
matching git tag for container “colorado.0.15” and there is no matching 
container for git tag “colorado.3.0”.
Also not clear what yardstick project will do to publish a newer version of the 
yardstick container for Danube 3.0?

Project owners should be able to publish finer grain versions of containers in 
a faster pace than the overall OPNFV release (e.g. as frequent as more than 
once a day) and these need to be tracked properly.

The best practice – as seen by most popular container images – is to tag the 
container using a version string that reflects the container source code 
version.
Translating to a project workflow, what is typical:

  *   The project repo uses git tags to version the source code (e.g. “3.2.5”) 
independently of the OPNFV release versioning (e.g. “Danube 3.0”). Such 
versioning sh

Re: [opnfv-tech-discuss] Multiple docker containers from one project

[Fatih Degirmenci]

ch-discuss] Multiple docker containers from one project

I'm sorry I don't understand the point of git clone.
Here we simply install Functest via the python package.
Pip install does a local copy because it's not published in PyPI yet and then 
removes it after installing the package.

Why should we clone again the repository?

Cédric

2017-07-10 3:10 GMT+02:00 Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>:
Why should we avoid copy?  Why do a git clone of the existing git clone?  
Almost every dockerfile example I have seen uses copy, not a second got 
checkout of the same code.
Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 9, 2017, at 21:00, Cedric OLLIVIER 
<ollivier.ced...@gmail.com<mailto:ollivier.ced...@gmail.com>> wrote:
No we cannot (parent directory) and we should mostly avoid copying files 
(except for configurations).

For instance, you could have a look to 
https://gerrit.opnfv.org/gerrit/#/c/36963/.
All Dockerfiles simply download Alpine packages, python packages (Functest + 
its dependencies) and upper constraints files.
testcases.yaml is copied from host as it differs between our containers (smoke, 
healthcheck...).
Cédric


2017-07-10 1:25 GMT+02:00 Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>:
My only concern is for dockerfiles that do a "COPY . /home" in them. That means 
all the code would be located under the docker directory.

I suppose multiple ../ paths can be used instead.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 9, 2017, at 19:03, Julien 
<julien...@gmail.com<mailto:julien...@gmail.com>> wrote:
Hi Cédric,

Patch in  https://gerrit.opnfv.org/gerrit/#/c/36963/ is exact what I mean. 
Let's collect the opinions from the releng team.

Julien



Cedric OLLIVIER 
<ollivier.ced...@gmail.com<mailto:ollivier.ced...@gmail.com>>于2017年7月10日周一 
上午4:15写道：
Hello,

Please see https://gerrit.opnfv.org/gerrit/#/c/36963/ which introduces several 
containers for Functest too.
I think the tree conforms with the previous requirements.

Automating builds on Docker Hub is a good solution too.
Cédric

2017-07-09 12:10 GMT+02:00 Julien 
<julien...@gmail.com<mailto:julien...@gmail.com>>:
Hi Jose,

According to the current implementation, current script only support one 
Dockerfile, my personal suggestion is:
1. list all the sub-directory which contains "Dockerfile"
2. build for each sub-directory fetched in #1
3. for the names, in the top directory using the project name, in the 
sub-directory using: project_name-sub_directory_name
not too much changes for current script and easy for project to manage.

/Julien

Beierl, Mark <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>于2017年7月7日周五 
下午11:35写道：
Hello,

Having looked over the docker-hub build service, I also think this might be the 
better approach.  Less code for us to maintain, and the merge job from OPNFV 
Jenkins can use the web hook to remotely trigger the job on docker-hub.

Who has the opnfv credentials for docker-hub, and the credentials for the 
GitHub mirror that can set this up?  Is that the LF Helpdesk?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 7, 2017, at 11:01, Xuan Jia 
<jason.jiax...@gmail.com<mailto:jason.jiax...@gmail.com>> wrote:

+1 Using build service from docker-hub

On Thu, Jul 6, 2017 at 11:42 PM, Yujun Zhang (ZTE) 
<zhangyujun+...@gmail.com<mailto:zhangyujun+...@gmail.com>> wrote:
Does anybody consider using the build service from docker-hub[1] ?

It supports multiple Dockerfile from same repository and easy to integrate with 
OPNFV Github mirror.

[1]: https://docs.docker.com/docker-hub/builds/


On Thu, Jul 6, 2017 at 11:02 PM Jose Lausuch 
<jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>> wrote:
Hi Mark,

I would incline for option 1), it sounds better than searching for a file. We 
could define specific values of DOCKERFILE var for each project.

/Jose


From: Beierl, Mark [mailto:mark.bei...@dell.com<mailto:mark.bei...@dell.com>]
Sent: Thursday, July 06, 2017 16:18 PM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Julien <julien...@gmail.com<mailto:julien...@gmail.com>>; Fatih Degirmenci 
<fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>>; Jose 
Lausuch <jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>>
Subject: Re: [opnfv-tech-discuss] Multiple docker containers from one project

Ideas:


  *   Change the DOCKERFILE parameter in re

Re: [opnfv-tech-discuss] VM image file server in OPNFV?

[Fatih Degirmenci]

Hi,

We store this type of artifacts on OPNFV Artifact Repository which is hosted on 
Google Cloud Storage.

http://artifacts.opnfv.org/octopus/docs/octopus_docs/opnfv-artifact-repository.html

Please send a ticket to OPNFV Helpdesk with the details so they can help you.

/Fatih

From:  on behalf of "Alec Hothan 
(ahothan)" 
Date: Monday, 10 July 2017 at 18:00
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] VM image file server in OPNFV?


Hello,

I was wondering if there a file server in OPNFV that can be used by OPNFV 
project owners to store public VM Images (several hundred MBs to 1 GB per 
image) that can be accessed internally (from OPNFV labs) and from the Internet?
OpenStack has a similar server (OpenStack App Catalog).

Thanks

  Alec


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

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

[Fatih Degirmenci]

+1

/Fatih

On 30 Jun 2017, at 10:12, Rossella Sblendido  wrote:

+1

Rossella

> On 06/29/2017 11:01 PM, Ross Brattain wrote:
> +1
> 
> --
> 
> Ross Brattain (proxy for Jack Morgan)
> 
> 
> On 06/29/2017 01:59 PM, David McBride wrote:
> +Ross
> 
> On Thu, Jun 29, 2017 at 12:21 PM, Tim Irnich  > wrote:
> 
>+1
> 
>Regards, Tim
> 
>Von meinem iPhone gesendet
> 
>Am 29.06.2017 um 17:05 schrieb Frank Brockners (fbrockne)
>>:
> 
>>+1
>> 
>>Frank
>> 
>>Am 28.06.2017 um 11:12 schrieb David McBride
>>>:
>> 
>>>TSC,
>>> 
>>>After examining status and considering various alternatives, Ray
>>>and I have agreed to propose July 14 as the new release date for
>>>Danube 3.  We believe that this will give project and installer
>>>teams time to overcome current issues, as well as allowing us to
>>>avoid the 4th of July holiday in the U.S., when many community
>>>members will be away on vacation.
>>> 
>>>Assuming that the TSC approves this change, then I would suggest
>>>the following schedule:
>>> 
>>>  * July 12 - complete testing
>>>  * July 13 - finish document updates / update JIRA
>>>  * July 14 - tag repos and release
>>>  * Week of July 17 - download page goes live
>>> 
>>>TSC members, *please respond to this email with your vote on the
>>>following by EOD PT June 30*:
>>> 
>>>Does the TSC approve moving the Danube 3.0 release date to
>>>July 14th? (+1, 0, -1)
>>> 
>>>David
>>> 
>>>-- 
>>>*David McBride*
>>>Release Manager, OPNFV
>>>Mobile: +1.805.276.8018 
>>>Email/Google Talk: dmcbr...@linuxfoundation.org
>>>
>>>Skype: davidjmcbride1
>>>IRC: dmcbride
>>>___
>>>opnfv-tech-discuss mailing list
>>>opnfv-tech-discuss@lists.opnfv.org
>>>
>>>https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>
>>___
>>opnfv-tsc mailing list
>>opnfv-...@lists.opnfv.org 
>>https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>>
> 
> 
> 
> 
> -- 
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018 
> Email/Google Talk: dmcbr...@linuxfoundation.org
> 
> Skype: davidjmcbride1
> IRC: dmcbride
> 
> 
> 
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 
___
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] [OPNFV] Draft support for presentation to TSC

[Fatih Degirmenci]

el) 
> <gabriel.yuy...@huawei.com<mailto:gabriel.yuy...@huawei.com>> wrote:
>
> Hi Morgan,
>
> Thanks for the information! Please find my version of the slides deck 
> attached.
> In addition, I have installed Libre office. Feel awesome!!
>
> @All Feel free to do any change needed.
>
>
> Best,
> Gabriel
>
> -Original Message-
> From: morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> 
> [mailto:morgan.richo...@orange.com]
> Sent: Friday, June 23, 2017 3:36 PM
> To: Yuyang (Gabriel); Brattain, Ross B; Gaoliang (kubi); Jose Lausuch; 
> Cooper, Trevor; MORTON, ALFRED C (AL); 
> mark.bei...@emc.com<mailto:mark.bei...@emc.com>; Fatih Degirmenci; Donald 
> Hunter (donaldh); Yujun Zhang
> Cc: test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>; 
> opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
> Subject: Re: [OPNFV] Draft support for presentation to TSC
>
> the pptx version
> note you can open odp with Libre office, an free software alternative to 
> Microsoft office
>
> OK to add the list of stress tests under planning
>
> /Morgan
>
>  On 23/06/2017 09:19, Yuyang (Gabriel) wrote:
>> Hi Morgan,
>>
>> Sure, I can present the beginning for the stress test in Danube.
>> One quick question, do we need to add a brief list for the stress test cases 
>> under planning?
>>
>> By the way, do you have a pptx version of your slides? So that we can modify 
>> the slides cooperatively. The odp version looks dark and a mess in my office 
>> 2013.
>>
>> Thanks,
>> Gabriel
>>
>>
>> -Original Message-----
>> From: morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> 
>> [mailto:morgan.richo...@orange.com]
>> Sent: Friday, June 23, 2017 2:39 PM
>> To: Yuyang (Gabriel); Brattain, Ross B; Gaoliang (kubi); Jose Lausuch;
>> Cooper, Trevor; MORTON, ALFRED C (AL); 
>> mark.bei...@emc.com<mailto:mark.bei...@emc.com>; Fatih
>> Degirmenci; Donald Hunter (donaldh); Yujun Zhang
>> Cc: test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>; 
>> opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
>> Subject: [OPNFV] Draft support for presentation to TSC
>>
>> Hi
>>
>> as discussed yesterday during the weekly meeting, I prepared a slide deck 
>> for the discussion with the TSC (I tried to summarize our discussion and 
>> hope it reflects the wiki pages we created on the topic).
>>
>> Feel free to comment/complete/criticize/modify
>> @Gabriel: would you be OK to present the beginning? (stress tests
>> created for Danube + wiki page and email thread)
>>
>> I already booked a slot for the meeting next week
>> https://wiki.opnfv.org/display/meetings/TSC
>> the agenda looks already pretty busy not sure we will have time, we
>> will see
>>
>> /Morgan
>>
>>
>>
>> __
>> ___
>>
>> Ce message et ses pieces jointes peuvent contenir des informations 
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
>> exploites ou copies sans autorisation. Si vous avez recu ce message par 
>> erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les 
>> pieces jointes. Les messages electroniques etant susceptibles d'alteration, 
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
>> falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged 
>> information that may be protected by law; they should not be distributed, 
>> used or copied without authorisation.
>> If you have received this email in error, please notify the sender and 
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been 
>> modified, changed or falsified.
>> Thank you.
>>
>
> --
> Morgan Richomme
> Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>
> Network architect for innovative services Future of the Network community 
> member Open source Orange community manager
>
>
> tel. +33 (0) 296 072 106
> mob. +33 (0) 637 753 326
> morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc pas

Re: [opnfv-tech-discuss] multi-site next step ?

[Fatih Degirmenci]

Hi Joe,

As Valentin summarized, XCI uses OSA directly from upstream and deploys 
OpenStack from master so there is no dependency to OPNFV installers. All the 
features/scenarios are/will be implemented in upstream, getting part of the 
upstream.

XCI provides sandbox for the developers to use to  integrate their features to 
upstream OSA. It is available for quite some time and used for adding support 
for ODL, Tacker, OVS NSH and enabling SFC. Sandbox lets you deploy OpenStack 
using VMs with number of different flavors. Baremetal also works and we will 
enable those jobs in OPNFV CI soon.

The provisioning is done by bifrost (standalone ironic) which is an upstream 
project as well.

We are also in the process of setting up 3rd Party CI for OSA which will 
provide feedback on the patches you and/or others might be proposing to 
upstream from OPNFV directly on OpenStack Gerrit.

You can take a look at the documentation from below links and ask any questions 
you might have via mail or on #opnfv-pharos irc channel.

https://wiki.opnfv.org/display/INF/OpenStack
https://wiki.opnfv.org/display/INF/XCI+Developer+Sandbox

/Fatih

On 23 Jun 2017, at 09:28, joehuang <joehu...@huawei.com> wrote:

Hi, Valentin,

Good idea, would like to know how many installers support OSA(OpenStack 
Ansible), and contributors are needed :)

Best Regards
Chaoyi Huang (joehuang)
From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 22 June 2017 20:06
To: joehuang; opnfv-tech-discuss
Cc: BLAISONNEAU David IMT/OLN; Fatih Degirmenci
Subject: RE:[opnfv-tech-discuss] multi-site next step ?

Hello Chaoyi,

It's great summary of all work in OPNFV and also in OpenStack Tricircle ! 

For my part, I use Tricircle for the OPNFV demo, and I think the current 
fonctionnality is fine ! Of course, I found some bugs and now it's fixed.

I think for the next step, It's more the integration and deployment of an 
OpenStack with Tricircle. Yes, it can be supported with OPNFV installer but I 
think the best way is to integrate that in OpenStack upstream installer like 
openstack-ansible. Tricircle is an OpenStack project so the integration in OSA 
make sense. In addition, some people in the community works on the integration 
of OSA in OPNFV (Fatih and Yolanda and several Suse guys on XCI and David 
Blaisonneau with OSA on baremetal). It would be cool to have a 
os-nosdn-multisite-ha scenario based on OSA!

We can also deploy tricircle in real context, like Windriver guys aksing in the 
end of our session. 2 or more site with some latency between each site.

Best regards,
Valentin 
De : opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de joehuang 
[joehu...@huawei.com]
Envoyé : jeudi 22 juin 2017 08:59
À : opnfv-tech-discuss
Objet : [opnfv-tech-discuss] multi-site next step ?

Hello,

After several cycles running of the multi-site project, in last week OPNFV 
summit, we demonstrate mission critical application video-conference and vIMS 
running in multi-region (multi-site) environment, and leverage the L2/L3  
networking capability provided by Tricircle, the two applications can achieve 
high availability ( active-active, or multi-master ) across multi-region.

The presentation video is here: https://www.youtube.com/watch?v=tbcc7-eZnkY, 
the slides is here: 
https://docs.google.com/presentation/d/1WBdra-ZaiB-K8_m3Pv76o_jhylEqJXTTxzEZ-cu8u2A/
 And a video was recorded for video conference: 
https://www.youtube.com/watch?v=nK1nWnH45gI, and vIMS video is in recording.

If you compare what happened in Amazon AWS for mission critical applications: 
slides 
https://www.slideshare.net/AmazonWebServices/aws-reinvent-2016-moving-mission-critical-apps-from-one-region-to-multiregion-activeactive-arc309,
 video https://www.youtube.com/watch?v=tBM5MB22vik, you will found that the use 
case tried to deploy the PS store and  database back-end Casandra into two 
regions, with Casandra running in active-active mode, communicating with each 
other through EIP(same as FIP in OpenStack) in different region. In our demo, 
vIMS is also using Casandra, and also deployed with active-active in two 
OpenStack region, but Tricricle provide more flexible internal tenant level 
isolated L2/L3 networking across region, and support more versatile and 
flexible networking topology. To deal with mission critical application running 
inside cloud, we are not alone, Tricircle even provides some better capability 
to some extent.

We can have summary for what have done in the multi-site project, there are so 
many people contributing in the past for these 5 use cases which were discussed 
during the initiation of multi-site project:
Use case 1: multisite identity service management(Shared KeyStone in demo)
Use case 2: VNF high availability across VIM (vIMS & JITSI in demo, cross 
OpenStack L2/L3 networking provided by Tricircle)
Use case 3: Multisite VNF Geo site disaster recovery (not covered, covered by 

Re: [opnfv-tech-discuss] TSC vote requested for security fix

[Fatih Degirmenci]

+1
No preference.

/Fatih

On 21 Jun 2017, at 08:28,  
 wrote:

+1
no preference

Morgan

> On 21/06/2017 06:54, Stuart Mackie wrote:
> +1 - Either
>  
> Stuart
> -914 886 2534
>  
> From:  on behalf of Raymond Paik 
> 
> Date: Tuesday, June 20, 2017 at 3:07 PM
> To: "opnfv-...@lists.opnfv.org" 
> Cc: "opnfv-tech-discuss@lists.opnfv.org" 
> Subject: [opnfv-tech-discuss] TSC vote requested for security fix
>  
> OPNFV TSC Members:
>  
> Sorry for the short notice, but earlier today the Linux Foundation IT team 
> has been made aware of a high priority security issue (see 
> https://access.redhat.com/security/vulnerabilities/stackguard) and need to 
> apply package errata and perform systems reboot as soon as possible.  We 
> tentatively scheduled 1-hour window on June 24th @01:00 - 02:00 UTC for this 
> work, but if the TSC agrees, we'd like fix this sooner.  
>  
> I realize the timing is not ideal as people are working on Danube 3.0, but 
> two options I'd like to propose are 22:00 - 23:00 UTC on June 21st or June 
> 22nd.  
>  
> Could I ask the TSC members to send your votes on the following as soon as 
> possible?
> · Do you approve an earlier security fix window? (Y/N)
> · If you answered Y above, are you OK with June 21st, June 22nd, or 
> are you OK with either?
> Thanks, 
>  
> Ray
>  
>  
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

-- 
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA 

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com
_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.
___
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] Multiple docker containers from one project

[Fatih Degirmenci]

Hi Mark,

It is perfectly fine to have different build processes and/or number of 
artifacts for the projects from releng point of view.

Once you decide what to do for storperf, we can take a look and adapt docker 
build job/script to build storperf images, create additional repos on docker 
hub to push images and activate the builds when things are ready.

/Fatih

On 20 Jun 2017, at 19:18, Beierl, Mark  wrote:

Hello,

I'd like to poll the various groups about ideas for how to handle this 
scenario.  I have interns working on breaking down services from StorPerf into 
different containers.  In one case, it will be a simple docker compose that is 
used to fire up existing containers from the repos, but the other case requires 
more thought.

We are creating a second container (storperf-reporting) that will need to be 
built and pushed to hub.docker.com.  Right now the build process for docker 
images lives in releng, and it only allows for one image to be built.  Should I 
be requesting a second git repo in this case, or should we look at changing the 
releng process to allow multiple docker images to be build?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
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


smime.p7s
Description: S/MIME cryptographic 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] Vote for the new Danube 3.0 release date

[Fatih Degirmenci]

+1

/Fatih

On 8 Jun 2017, at 03:04, Raymond Paik  wrote:

TSC members, 

Apologies for a little delay on this.  

As David communicated yesterday, he is recommending postponing the Danube 3.0 
release date to June 23rd (2-week delay) as community members experienced 
technical issues over the weekend.

I'd like to start an email vote among the TSC members on the following:

"Does the TSC approve changing the Danube 3.0 release date to June 23, 2017?  
(+1, 0, -1)"

Could you send me your vote by 6pm Pacific Time on June 8th (Thursday)?

Thanks, 

Ray
___
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] [SFC] Using openstack-ansible

[Fatih Degirmenci]

Hi Trinath,

First of all, thanks a lot for working on this!

I checked with osa guys and no work has been done for tacker role yet.

My suggestion to you is to take a look at the documentation explaining how
new roles can be contributed to osa. [1]
As explained in the documentation, you can start this work in our repos.
Once the basics are in place and working, we push it to upstream to get
their feedback and finalize the integration.
My proposal is to use opnfv/releng-xci repo for this work in a new
directory openstack-ansible-tacker. [2]

Please also join to the #openstack-ansible channel to ask osa questions
if/when you have them - all osa people are very responsive and helpful.
(they are also aware of what we are doing in OPNFV.)

[1]
https://docs.openstack.org/developer/openstack-ansible/developer-docs/additional-roles.html
[2] https://gerrit.opnfv.org/gerrit/gitweb?p=releng-xci.git;a=summary

/Fatih


On 25 May 2017 at 13:04, Manuel Buil <mb...@suse.com> wrote:

> We normally meet weekly on Wednesdays, 14:00 UTC
> <http://www.timeanddate.com/worldclock/fixedtime.html?hour=14=0=0>
>
> We are also in the IRC room: #opnfv-sfc
>
> Here you have more info:
> <https://wiki.opnfv.org/display/sfc/Service+Function+Chaining+Home>
> https://wiki.opnfv.org/display/sfc/Service+Function+Chaining+Home
>
> Regards,
> Manuel
>
>
> On Thu, 2017-05-25 at 10:02 +, Trinath Somanchi wrote:
>
> Hi Manuel-
>
>
>
> Sure. Is there any meeting room/time for this? So that I can share the
> work status.
>
>
>
> Thanks,
>
> *Trinath Somanchi.*
>
>
>
> Digital Networking | NXP – Hyderabad – INDIA.
>
> Email: *trinath.soman...@nxp.com <trinath.soman...@nxp.com>*
>
> Mobile: +91 9866235130 | Off: +91 4033504051
>
> [image: cid:image001.png@01D28854.B7934C80]
>
>
>
> *From:* Manuel Buil [mailto:mb...@suse.com]
> *Sent:* Thursday, May 25, 2017 3:20 PM
> *To:* Trinath Somanchi <trinath.soman...@nxp.com>; Fatih Degirmenci <
> fde...@gmail.com>; opnfv-tech-discuss@lists.opnfv.org; Juan Vidal ALLENDE
> <juan.vidal.alle...@ericsson.com>
> *Subject:* Re: [opnfv-tech-discuss] [SFC] Using openstack-ansible
>
>
>
> Hi Trinath,
>
>
>
> I have been talking to Juan and we think that it would be great if you
> help with tacker and as you have experience with it, probably you will be
> able to do it very quickly. Starting next week I want to focus on
> openstack-ansible too, so if I could help you in any way, please tell me.
>
>
>
> If possible, we would like to have a first version of tacker running with
> openstack-ansible by mid-June, so that we have some room to test and fix
> bugs which might appear when integrating everything. Do you think you could
> have the time to do it?
>
>
>
> Thanks,
>
> Manuel
>
>
>
> On Thu, 2017-05-25 at 05:42 +, Trinath Somanchi wrote:
>
> I see that there is no active work on this, https://review.openstack.org/#
> /q/topic:bp/role-tacker,n,z
>
>
>
> If there is no active contribution at OSA at Tacker front, I can take up
> this task.
>
>
>
> Please let me know the timelines to accomplish this task.
>
>
>
> I’m Currently working on Tacker, http://stackalytics.com/?
> module=tacker-group
>
>
>
> Thanks,
>
> *Trinath Somanchi.*
>
>
>
> Digital Networking | NXP – Hyderabad – INDIA.
>
> Email: *trinath.soman...@nxp.com <trinath.soman...@nxp.com>*
>
> Mobile: +91 9866235130 | Off: +91 4033504051
>
> [image: cid:image001.png@01D28854.B7934C80]
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> <opnfv-tech-discuss-boun...@lists.opnfv.org>] *On Behalf Of *Fatih
> Degirmenci
> *Sent:* Wednesday, May 24, 2017 9:00 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org; Juan Vidal ALLENDE <
> juan.vidal.alle...@ericsson.com>
> *Subject:* Re: [opnfv-tech-discuss] [SFC] Using openstack-ansible
>
>
>
> Hi,
>
>
>
> About tacker support for osa; there is a blueprint for this already which
> we can try to find out the latest status and work with the osa community in
> order to move it forward.
>
> https://blueprints.launchpad.net/openstack-ansible/+spec/role-tacker
>
>
>
> /Fatih
>
>
> On 24 May 2017, at 17:15, Juan Vidal ALLENDE <juan.vidal.allende@ericsson.
> com> wrote:
>
> Hello,
>
>
>
> As we talked today in our weekly meeting, there are some tasks that need
> to be in place to have a working environment. These are the ones that come
> to my mind right now, feel free to reply and discuss anything else that you
> find necessary.
>
>
>
>  - Install ODL wi

Re: [opnfv-tech-discuss] [SFC] Using openstack-ansible

[Fatih Degirmenci]

Hi,

About tacker support for osa; there is a blueprint for this already which we 
can try to find out the latest status and work with the osa community in order 
to move it forward.

https://blueprints.launchpad.net/openstack-ansible/+spec/role-tacker

/Fatih

On 24 May 2017, at 17:15, Juan Vidal ALLENDE  
wrote:

Hello,

As we talked today in our weekly meeting, there are some tasks that need to be 
in place to have a working environment. These are the ones that come to my mind 
right now, feel free to reply and discuss anything else that you find necessary.

 - Install ODL with OSA (Juan)
 - Install Tacker with OSA
 - Add support for NSH in OpenVSwitch
 - Install VPP with OSA?
 - Add support to utilities in the same way as we had with Fuel (SSH, access to 
controller/computes...)

If you think that you can help with any of this tasks, please reply to this 
email to keep the team informed.

Regards,
Juan
___
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] 答复: [announce] OPNFV maintenance window 2017-05-21 17:00 - 21:00 UTC

[Fatih Degirmenci]

Hi,

There are other failures as well.

https://build.opnfv.org/ci/job/compass-os-nosdn-nofeature-ha-baremetal-daily-master/487/console

/Fatih

On 22 May 2017 at 06:05,  wrote:

> Hello,
>
> Could you please also check the following issue raised by
> functest-verify-master? (It may be directly related to releng).
> https://build.opnfv.org/ci/job/functest-verify-master/4135/console
>
> git tag -a -f -m Jenkins Build #4135 jenkins-functest-verify-master-4135
> # timeout=10 FATAL: Could not apply tag jenkins-functest-verify-master-4135
> hudson.plugins.git.GitException
> :
> Command "git tag -a -f -m Jenkins Build #4135 
> jenkins-functest-verify-master-4135"
> returned status code 128: stdout: stderr: *** Please tell me who you are.
> Run git config --global user.email "y...@example.com" git config --global
> user.name "Your Name" to set your account's default identity. Omit
> --global to set the identity only in this repository. fatal: unable to
> auto-detect email address (got 'jenkins@ci-jenkins-build-4.(none)')
>
> Thank you. Best Regards
> Cédric OLLIVIER
>
> On lun., 2017-05-22 at 02:13 +, Lijun (Matthew) wrote:
>
> hi
>
> It seems Jenkins releng-deploy-sandbox job is blocked by no nodes with
> 'releng-sandbox' label,  leads to releng jobs have no verify votes. Can
> anyone to take a look?
>
> best regards
>
> MatthewLi
> *发件人：*Ryan Finnin Day
> *收件人：*it-infrastructure-ale...@linuxfoundation.org,Motamary, Shabrinath
> via opnfv-tech-discuss,infra...@lists.opnfv.org
> *时间：*2017-05-22 03:07:10
> *主题:*Re: [opnfv-tech-discuss] [announce] OPNFV maintenance window
> 2017-05-21 17:00 - 21:00 UTC
>
> This work is complete.
>
> Thank you for your patience.
>
> Ryan
>
> On 05/21/2017 09:32 AM, Ryan Finnin Day wrote:
> > This work will be starting soon.
> >
> > On 05/15/2017 04:43 PM, Ryan Finnin Day wrote:
> >> What:
> >>
> >>   The Linux Foundation will be performing needed maintenance on servers
> >> hosting OPNFV services.
> >>
> >> When:
> >>
> >>   Sunday, May 21 @ 10:00 - 14:00 PDT (2017-05-21 17:00 - 21:00 UTC)
> >>
> >> Why:
> >>
> >>   There are system updates available to be applied to systems hosting
> >> OPNFV services.
> >>
> >> Impact:
> >>
> >>   The following services will be impacted by system updates and reboots
> >> during the maintenance window:
> >>   - Confluence
> >>   - Etherpad
> >>   - Gerrit
> >>   - Jenkins
> >>   - Jira
> >>
> >>
> >> Notices will be posted here at the start and end of the maintenance.
> >>
> >>
> >>
> >>
> >>
> >
>
> ___
> opnfv-tech-discuss mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://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

[opnfv-tech-discuss] What is Bifrost: Video from OpenStack Summit

[Fatih Degirmenci]

Hi,

Here is the link to the recording of Bifrost session which gives a quick 
overview.

https://youtu.be/Rk9QqEzgpgY

There are few references to OPNFV as well.

/Fatih

smime.p7s
Description: S/MIME cryptographic 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] [OPNFV] Split of releng repo?

[Fatih Degirmenci]

Hi,

This is still the plan. The reason why this hasn't happened yet is Danube.

I'll share the analysis soon and then we can do this once Danube.3.0 is out.

/Fatih

On 5 May 2017, at 10:54, "morgan.richo...@orange.com" 
 wrote:

Hi

I think we already initiated this discussion some times ago
but would it make sense to split releng repo into releng-jjb and
releng-utils
as there are at least 2 very different areas (jenkins and Xproject
tooling/lib)

/Morgan

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Henry Four
 ie:MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Randy Leve
 nsalor:MAILTO:r.levensa...@cablelabs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Afek, Ifat
  (Nokia - IL/Kfar Sava)":MAILTO:ifat.a...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rgrigar@li
 nuxfoundation.org:MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Paparao.Pa
 lacha...@us.fujitsu.com:MAILTO:paparao.palacha...@us.fujitsu.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Skerry, Br
 ian J":MAILTO:brian.j.ske...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Suren Vyas
  (svyas):MAILTO:sv...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=James Buch
 anan:MAILTO:jbucha...@advaoptical.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Robert Dim
 ond:MAILTO:robert.dim...@arm.com
DESCRIPTION;LANGUAGE=en-GB:Cancelling this week's meeting due to OPNFV Hack
 fest.\n\n/Fatih\n\nThe "Infra Working Group" plans and tracks infrastructu
 re cross project initiatives.\nWe report our efforts up to the TSC to ensu
 re the community is able to provide sufficient resources for development a
 nd release infrastructure.\n\nTopics and meeting agenda at https://wiki.op
 nfv.org/display/INF/Infra+Working+Group\nMinutes at Infra Working Group Me
 eting<https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting>
 \n? Weekly on Monday at 8:00 PST or 15:00 UTC (during US daylight 
 saving)\n? GTM Link https://global.gotomeeting.com/join/819733085\
 n?     IRC #opnfv-meeting - freenode.net<http://freenode.net/>\n? 
 Chaired by Fatih Degirmenci<https://wiki.opnfv.org/display/~fdegir> (m
 eetings chaired by Infra PTLs on a 2-month basis)\n? You can also 
 dial in using your phone with Access Code: 819-733-085\n\n\no   

Re: [opnfv-tech-discuss] Daily jobs for two streams

[Fatih Degirmenci]

Hi Mark,

The no of executors for your pod9 slave has been changed from 2 to 1 now.

https://build.opnfv.org/ci/computer/intel-pod9/

From now on, if Jenkins triggers the danube job while job for the master is 
running, danube job will wait in the queue until job for the master ends and 
vice versa.

We normally use build blocker to prevent concurrent executions of the same type 
of jobs using same slave but in your case we don't need this.

/Fatih

From:  on behalf of "Beierl, Mark" 

Date: Wednesday, 29 March 2017 at 16:49
To: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] Daily jobs for two streams

I have a bit of a dilemma for StorPerf.  I only have one pod to run the daily 
jobs on, and it seeks to push the capacity of the Ceph storage, so I can only 
have one job running at time.  But what I cannot see is how to stagger the 
start times for the daily master and daily danube jobs.  From what I can see, 
the Danube job attempts to start 1 hour after the master job has started, 
resulting in job collisions.

How do I stagger them using the jjb, or how do other projects deal with this?

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] Infra Working Group Meeting

[Fatih Degirmenci]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Fatih Degirmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-GB:The "Infra Working Group" plans and tracks infra
 structure cross project initiatives.\n\nWe report our efforts up to the TS
 C to ensure the community is able to provide sufficient resources for deve
 lopment and release infrastructure.\n\n\n\nTopics and meeting agenda at ht
 tps://wiki.opnfv.org/display/INF/Infra+Working+Group\n\nMinutes at Infra W
 orking Group Meeting<https://wiki.opnfv.org/display/meetings/Infra+Working
 +Group+Meeting>\n\n\n   *   Weekly on Monday at 8:00 PST or 15:00 UTC (dur
 ing US daylight saving)\n\n   *   GTM Link https://global.gotomeeting.com/
 join/819733085\n\n   *   IRC #opnfv-meeting - freenode.net<http://freenode
 .net/>\n\n   *   Chaired by Fatih Degirmenci<https://wiki.opnfv.org/displa
 y/~fdegir> (meetings chaired by Infra PTLs on a 2-month basis)\n\n   *   Y
 ou can also dial in using your phone with Access Code: 819-733-085\n\n\n\n
 *   United States +1 (312) 757-3126\n\n*   Australia +61 2
  8355 1040\n\n*   Austria +43 7 2088 0034\n\n*   Belgium +
 32 (0) 28 93 7018\n\n*   Canada +1 (647) 497-9350\n\n*   D
 enmark +45 69 91 88 64\n\n*   Finland +358 (0) 923 17 0568\n\n
 *   France +33 (0) 170 950 592\n\n*   Germany +49 (0) 692 5736
  7211\n\n*   Ireland +353 (0) 15 360 728\n\n*   Italy +39 
 0 247 92 13 01\n\n*   Netherlands +31 (0) 208 080 219\n\n*
New Zealand +64 9 280 6302\n\n*   Norway +47 75 80 32 07\n\n   
  *   Spain +34 911 82 9906\n\n*   Sweden +46 (0) 853 527 836\n
 \n*   Switzerland +41 (0) 435 0167 13\n\n*   United Kingdo
 m +44 (0) 330 221 0086\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20170425T15Z;INTERVAL=1;BYDAY=MO;WKST=SU
UID:EA5813C2-EBF5-45EA-895D-AB018F7785FA
SUMMARY;LANGUAGE=en-GB:Infra Working Group Meeting
DTSTART;TZID=W. Europe Standard Time:20170327T17
DTEND;TZID=W. Europe Standard Time:20170327T18
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170322T175258Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-GB:GTM and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115221407
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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