Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

2019-05-10 Thread David McBride 
Amar has collected feedback from PTLs here:
https://wiki.opnfv.org/display/SWREL/Hunter+Release+Key+Updates.  Brandon
is working on the Hunter messaging and will be discussing that in the next
TSC meeting.

As is often the case with a releease, we are still reaching out to the
projects to make sure that they have completed their documentation and have
updated the documentation compliance page.

David

On Thu, May 9, 2019 at 4:40 PM Cooper, Trevor 
wrote:

> Hi David
>
>
>
> I think Frank has a point, before each release don’t we normally have a
> statement available of what is new in the release (collected from PTLs)?
> Looking at the documentation compliance page the final documentation
> milestone lists 8 out of the 24 projects in the release? Is that because 16
> projects don’t have any updates to document?
>
>
>
> /Trevor
>
>
>
>
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *David McBride
> *Sent:* Thursday, May 9, 2019 7:12 AM
> *To:* Frank Brockners (fbrockne) 
> *Cc:* TSC OPNFV ; Bin Hu ;
> TECH-DISCUSS OPNFV 
> *Subject:* Re: [opnfv-tech-discuss] status of Hunter release #hunter
> #release
>
>
>
> Sure, I can do that.
>
>
>
> I expect that we will have a similar set of artifacts to what is
> documented on the download page for the previous release, and what's
> reported on the documentation compliance page, minus artifacts from
> projects that have withdrawn from the release or left OPNFV, but that
> varies somewhat from release-to-release. The largest degree of uncertainty
> is with new projects.
>
>
>
> David
>
>
>
> On Thu, May 9, 2019 at 7:01 AM Frank Brockners (fbrockne) <
> fbroc...@cisco.com> wrote:
>
> David,
>
>
>
> Thanks – could you supply the Jenkins links?
> If I understand your email correctly, you say that apart from the
> scenarios, we don’t really know what we’d release, correct?
>
>
>
> Thanks, Frank
>
>
>
> *From:* David McBride 
> *Sent:* Donnerstag, 9. Mai 2019 15:51
> *To:* Frank Brockners (fbrockne) 
> *Cc:* TSC OPNFV ; Bin Hu ;
> TECH-DISCUSS OPNFV 
> *Subject:* Re: [opnfv-tech-discuss] status of Hunter release #hunter
> #release
>
>
>
> Frank,
>
>
>
> For the past several releases, I've relied on deployment and health check
> status for each scenario as reported by Jenkins. Scenario owners consider
> all test results and decide whether to release and communicate that intent,
> for each scenario, on the scenario status page.
>
>
>
> If projects submit an intent-to-participate, and don't withdraw from the
> release, then I presume that they will have deliverables.  We don't require
> projects to provide a comprehensive list of deliverables in their release
> plan, so I don't have that information, aside from what's reported on the
> scenario status page, and the documentation compliance page.
>
>
>
> David
>
>
>
> On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) <
> fbroc...@cisco.com> wrote:
>
> David,
>
>
>
> Thanks for the summary. To be able to form an opinion on how to vote,
> could you supply the following additional information?
>
>
>
> On the scenarios: Could you supply a pointer to the test results? E.g.
> http://testresults.opnfv.org/master/functest/status-apex.html  is found
> empty.
>
>
>
> On the additional artefacts: Could you supply a list of the artefacts you
> refer to below along with the draft documentation that we are planning to
> release? Without that info it is a little difficult to understand what the
> release will comprise and whether the listed projects will indeed supply
> something that is consumable. E.g. FDS, despite listed, will not release
> any artefact for Hunter.
>
>
>
> Thanks, Frank
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *David McBride
> *Sent:* Mittwoch, 8. Mai 2019 22:49
> *To:* TSC OPNFV 
> *Cc:* Bin Hu ; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject:* [opnfv-tech-discuss] status of Hunter release #hunter #release
>
>
>
> Team,
>
>
>
> I took an action in Tuesday's TSC meeting to publish the status of the
> Hunter release.
>
>
>
> The following scenarios are passing deployment and health check:
>
>
>
> *Scenario*
>
> *Installer*
>
> os-nosdn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Apex
>
> os-ovn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Fuel@x86
>
> os-nosdn-ovs-noha
>
> Fuel@x86
>
> os-odl-nofeatur

Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

2019-05-09 Thread Cooper, Trevor 
Hi David

I think Frank has a point, before each release don’t we normally have a 
statement available of what is new in the release (collected from PTLs)? 
Looking at the documentation compliance page the final documentation milestone 
lists 8 out of the 24 projects in the release? Is that because 16 projects 
don’t have any updates to document?

/Trevor



From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of David McBride
Sent: Thursday, May 9, 2019 7:12 AM
To: Frank Brockners (fbrockne) 
Cc: TSC OPNFV ; Bin Hu ; 
TECH-DISCUSS OPNFV 
Subject: Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

Sure, I can do that.

I expect that we will have a similar set of artifacts to what is documented on 
the download page for the previous release, and what's reported on the 
documentation compliance page, minus artifacts from projects that have 
withdrawn from the release or left OPNFV, but that varies somewhat from 
release-to-release. The largest degree of uncertainty is with new projects.

David

On Thu, May 9, 2019 at 7:01 AM Frank Brockners (fbrockne) 
mailto:fbroc...@cisco.com>> wrote:
David,

Thanks – could you supply the Jenkins links?
If I understand your email correctly, you say that apart from the scenarios, we 
don’t really know what we’d release, correct?

Thanks, Frank

From: David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Sent: Donnerstag, 9. Mai 2019 15:51
To: Frank Brockners (fbrockne) mailto:fbroc...@cisco.com>>
Cc: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>; 
Bin Hu mailto:bh5...@att.com>>; TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

Frank,

For the past several releases, I've relied on deployment and health check 
status for each scenario as reported by Jenkins. Scenario owners consider all 
test results and decide whether to release and communicate that intent, for 
each scenario, on the scenario status page.

If projects submit an intent-to-participate, and don't withdraw from the 
release, then I presume that they will have deliverables.  We don't require 
projects to provide a comprehensive list of deliverables in their release plan, 
so I don't have that information, aside from what's reported on the scenario 
status page, and the documentation compliance page.

David

On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) 
mailto:fbroc...@cisco.com>> wrote:
David,

Thanks for the summary. To be able to form an opinion on how to vote, could you 
supply the following additional information?

On the scenarios: Could you supply a pointer to the test results? E.g. 
http://testresults.opnfv.org/master/functest/status-apex.html  is found empty.

On the additional artefacts: Could you supply a list of the artefacts you refer 
to below along with the draft documentation that we are planning to release? 
Without that info it is a little difficult to understand what the release will 
comprise and whether the listed projects will indeed supply something that is 
consumable. E.g. FDS, despite listed, will not release any artefact for Hunter.

Thanks, Frank

From: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
On Behalf Of David McBride
Sent: Mittwoch, 8. Mai 2019 22:49
To: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>
Cc: Bin Hu mailto:bh5...@att.com>>; TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] status of Hunter release #hunter #release

Team,

I took an action in Tuesday's TSC meeting to publish the status of the Hunter 
release.

The following scenarios are passing deployment and health check:

Scenario

Installer

os-nosdn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Apex

os-ovn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Fuel@x86

os-nosdn-ovs-noha

Fuel@x86

os-odl-nofeature-noha

Fuel@x86

os-nosdn-nofeature-ha

Fuel@x86

os-nosdn-ovs-ha

Fuel@x86

os-odl-nofeature-ha

Fuel@x86


Other scenarios found on the scenario status 
page,<https://wiki.opnfv.org/display/SWREL/Hunter+Scenario+Status> planned for 
Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to 
deployment or HC failures.
In addition, the following projects will be providing artifacts for the Hunter 
release:
Apex

Barometer

Bottlenecks

C-RAN

Calipso

Clover

Container4NFV

Doctor

Edge Cloud

FDS

Fuel

Functest

High Availability

IPv6

NFVBench

OPNFVDOC

OVN4NFV

SampleVNF

SFC

SNAPS-OO

Stor4NFV

StorPerf

VSPerf

Yardstick


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<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride


--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org

Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

2019-05-09 Thread David McBride 
Sure, I can do that.

I expect that we will have a similar set of artifacts to what is documented
on the download page for the previous release, and what's reported on the
documentation compliance page, minus artifacts from projects that have
withdrawn from the release or left OPNFV, but that varies somewhat from
release-to-release. The largest degree of uncertainty is with new projects.

David

On Thu, May 9, 2019 at 7:01 AM Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> David,
>
>
>
> Thanks – could you supply the Jenkins links?
> If I understand your email correctly, you say that apart from the
> scenarios, we don’t really know what we’d release, correct?
>
>
>
> Thanks, Frank
>
>
>
> *From:* David McBride 
> *Sent:* Donnerstag, 9. Mai 2019 15:51
> *To:* Frank Brockners (fbrockne) 
> *Cc:* TSC OPNFV ; Bin Hu ;
> TECH-DISCUSS OPNFV 
> *Subject:* Re: [opnfv-tech-discuss] status of Hunter release #hunter
> #release
>
>
>
> Frank,
>
>
>
> For the past several releases, I've relied on deployment and health check
> status for each scenario as reported by Jenkins. Scenario owners consider
> all test results and decide whether to release and communicate that intent,
> for each scenario, on the scenario status page.
>
>
>
> If projects submit an intent-to-participate, and don't withdraw from the
> release, then I presume that they will have deliverables.  We don't require
> projects to provide a comprehensive list of deliverables in their release
> plan, so I don't have that information, aside from what's reported on the
> scenario status page, and the documentation compliance page.
>
>
>
> David
>
>
>
> On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) <
> fbroc...@cisco.com> wrote:
>
> David,
>
>
>
> Thanks for the summary. To be able to form an opinion on how to vote,
> could you supply the following additional information?
>
>
>
> On the scenarios: Could you supply a pointer to the test results? E.g.
> http://testresults.opnfv.org/master/functest/status-apex.html  is found
> empty.
>
>
>
> On the additional artefacts: Could you supply a list of the artefacts you
> refer to below along with the draft documentation that we are planning to
> release? Without that info it is a little difficult to understand what the
> release will comprise and whether the listed projects will indeed supply
> something that is consumable. E.g. FDS, despite listed, will not release
> any artefact for Hunter.
>
>
>
> Thanks, Frank
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *David McBride
> *Sent:* Mittwoch, 8. Mai 2019 22:49
> *To:* TSC OPNFV 
> *Cc:* Bin Hu ; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject:* [opnfv-tech-discuss] status of Hunter release #hunter #release
>
>
>
> Team,
>
>
>
> I took an action in Tuesday's TSC meeting to publish the status of the
> Hunter release.
>
>
>
> The following scenarios are passing deployment and health check:
>
>
>
> *Scenario*
>
> *Installer*
>
> os-nosdn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Apex
>
> os-ovn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Fuel@x86
>
> os-nosdn-ovs-noha
>
> Fuel@x86
>
> os-odl-nofeature-noha
>
> Fuel@x86
>
> os-nosdn-nofeature-ha
>
> Fuel@x86
>
> os-nosdn-ovs-ha
>
> Fuel@x86
>
> os-odl-nofeature-ha
>
> Fuel@x86
>
>
>
> Other scenarios found on the scenario status page,
> <https://wiki.opnfv.org/display/SWREL/Hunter+Scenario+Status> planned for
> Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to
> deployment or HC failures.
>
> In addition, the following projects will be providing artifacts for the
> Hunter release:
>
> Apex
>
> Barometer
>
> Bottlenecks
>
> C-RAN
>
> Calipso
>
> Clover
>
> Container4NFV
>
> Doctor
>
> Edge Cloud
>
> FDS
>
> Fuel
>
> Functest
>
> High Availability
>
> IPv6
>
> NFVBench
>
> OPNFVDOC
>
> OVN4NFV
>
> SampleVNF
>
> SFC
>
> SNAPS-OO
>
> Stor4NFV
>
> StorPerf
>
> VSPerf
>
> Yardstick
>
>
>
> 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*
>
> Relea

Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

2019-05-09 Thread Frank Brockners via Lists.Opnfv.Org 
David,

Thanks – could you supply the Jenkins links?
If I understand your email correctly, you say that apart from the scenarios, we 
don’t really know what we’d release, correct?

Thanks, Frank

From: David McBride 
Sent: Donnerstag, 9. Mai 2019 15:51
To: Frank Brockners (fbrockne) 
Cc: TSC OPNFV ; Bin Hu ; 
TECH-DISCUSS OPNFV 
Subject: Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

Frank,

For the past several releases, I've relied on deployment and health check 
status for each scenario as reported by Jenkins. Scenario owners consider all 
test results and decide whether to release and communicate that intent, for 
each scenario, on the scenario status page.

If projects submit an intent-to-participate, and don't withdraw from the 
release, then I presume that they will have deliverables.  We don't require 
projects to provide a comprehensive list of deliverables in their release plan, 
so I don't have that information, aside from what's reported on the scenario 
status page, and the documentation compliance page.

David

On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) 
mailto:fbroc...@cisco.com>> wrote:
David,

Thanks for the summary. To be able to form an opinion on how to vote, could you 
supply the following additional information?

On the scenarios: Could you supply a pointer to the test results? E.g. 
http://testresults.opnfv.org/master/functest/status-apex.html  is found empty.

On the additional artefacts: Could you supply a list of the artefacts you refer 
to below along with the draft documentation that we are planning to release? 
Without that info it is a little difficult to understand what the release will 
comprise and whether the listed projects will indeed supply something that is 
consumable. E.g. FDS, despite listed, will not release any artefact for Hunter.

Thanks, Frank

From: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
On Behalf Of David McBride
Sent: Mittwoch, 8. Mai 2019 22:49
To: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>
Cc: Bin Hu mailto:bh5...@att.com>>; TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] status of Hunter release #hunter #release

Team,

I took an action in Tuesday's TSC meeting to publish the status of the Hunter 
release.

The following scenarios are passing deployment and health check:

Scenario

Installer

os-nosdn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Apex

os-ovn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Fuel@x86

os-nosdn-ovs-noha

Fuel@x86

os-odl-nofeature-noha

Fuel@x86

os-nosdn-nofeature-ha

Fuel@x86

os-nosdn-ovs-ha

Fuel@x86

os-odl-nofeature-ha

Fuel@x86


Other scenarios found on the scenario status 
page,<https://wiki.opnfv.org/display/SWREL/Hunter+Scenario+Status> planned for 
Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to 
deployment or HC failures.
In addition, the following projects will be providing artifacts for the Hunter 
release:
Apex

Barometer

Bottlenecks

C-RAN

Calipso

Clover

Container4NFV

Doctor

Edge Cloud

FDS

Fuel

Functest

High Availability

IPv6

NFVBench

OPNFVDOC

OVN4NFV

SampleVNF

SFC

SNAPS-OO

Stor4NFV

StorPerf

VSPerf

Yardstick


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<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride


--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23119): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23119
Mute This Topic: https://lists.opnfv.org/mt/31547970/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter=2783016
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] status of Hunter release #hunter #release

2019-05-09 Thread David McBride 
Frank,

For the past several releases, I've relied on deployment and health check
status for each scenario as reported by Jenkins. Scenario owners consider
all test results and decide whether to release and communicate that intent,
for each scenario, on the scenario status page.

If projects submit an intent-to-participate, and don't withdraw from the
release, then I presume that they will have deliverables.  We don't require
projects to provide a comprehensive list of deliverables in their release
plan, so I don't have that information, aside from what's reported on the
scenario status page, and the documentation compliance page.

David

On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) <
fbroc...@cisco.com> wrote:

> David,
>
>
>
> Thanks for the summary. To be able to form an opinion on how to vote,
> could you supply the following additional information?
>
>
>
> On the scenarios: Could you supply a pointer to the test results? E.g.
> http://testresults.opnfv.org/master/functest/status-apex.html  is found
> empty.
>
>
>
> On the additional artefacts: Could you supply a list of the artefacts you
> refer to below along with the draft documentation that we are planning to
> release? Without that info it is a little difficult to understand what the
> release will comprise and whether the listed projects will indeed supply
> something that is consumable. E.g. FDS, despite listed, will not release
> any artefact for Hunter.
>
>
>
> Thanks, Frank
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *David McBride
> *Sent:* Mittwoch, 8. Mai 2019 22:49
> *To:* TSC OPNFV 
> *Cc:* Bin Hu ; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@lists.opnfv.org>
> *Subject:* [opnfv-tech-discuss] status of Hunter release #hunter #release
>
>
>
> Team,
>
>
>
> I took an action in Tuesday's TSC meeting to publish the status of the
> Hunter release.
>
>
>
> The following scenarios are passing deployment and health check:
>
>
>
> *Scenario*
>
> *Installer*
>
> os-nosdn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Apex
>
> os-ovn-nofeature-ha
>
> Apex
>
> os-nosdn-nofeature-noha
>
> Fuel@x86
>
> os-nosdn-ovs-noha
>
> Fuel@x86
>
> os-odl-nofeature-noha
>
> Fuel@x86
>
> os-nosdn-nofeature-ha
>
> Fuel@x86
>
> os-nosdn-ovs-ha
>
> Fuel@x86
>
> os-odl-nofeature-ha
>
> Fuel@x86
>
>
>
> Other scenarios found on the scenario status page,
>  planned for
> Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to
> deployment or HC failures.
>
> In addition, the following projects will be providing artifacts for the
> Hunter release:
>
> Apex
>
> Barometer
>
> Bottlenecks
>
> C-RAN
>
> Calipso
>
> Clover
>
> Container4NFV
>
> Doctor
>
> Edge Cloud
>
> FDS
>
> Fuel
>
> Functest
>
> High Availability
>
> IPv6
>
> NFVBench
>
> OPNFVDOC
>
> OVN4NFV
>
> SampleVNF
>
> SFC
>
> SNAPS-OO
>
> Stor4NFV
>
> StorPerf
>
> VSPerf
>
> Yardstick
>
>
>
> 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
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23118): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23118
Mute This Topic: https://lists.opnfv.org/mt/31547970/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter=2783016
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] status of Hunter release #hunter #release

2019-05-09 Thread Frank Brockners via Lists.Opnfv.Org 
David,

Thanks for the summary. To be able to form an opinion on how to vote, could you 
supply the following additional information?

On the scenarios: Could you supply a pointer to the test results? E.g. 
http://testresults.opnfv.org/master/functest/status-apex.html  is found empty.

On the additional artefacts: Could you supply a list of the artefacts you refer 
to below along with the draft documentation that we are planning to release? 
Without that info it is a little difficult to understand what the release will 
comprise and whether the listed projects will indeed supply something that is 
consumable. E.g. FDS, despite listed, will not release any artefact for Hunter.

Thanks, Frank

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of David McBride
Sent: Mittwoch, 8. Mai 2019 22:49
To: TSC OPNFV 
Cc: Bin Hu ; TECH-DISCUSS OPNFV 

Subject: [opnfv-tech-discuss] status of Hunter release #hunter #release

Team,

I took an action in Tuesday's TSC meeting to publish the status of the Hunter 
release.

The following scenarios are passing deployment and health check:

Scenario

Installer

os-nosdn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Apex

os-ovn-nofeature-ha

Apex

os-nosdn-nofeature-noha

Fuel@x86

os-nosdn-ovs-noha

Fuel@x86

os-odl-nofeature-noha

Fuel@x86

os-nosdn-nofeature-ha

Fuel@x86

os-nosdn-ovs-ha

Fuel@x86

os-odl-nofeature-ha

Fuel@x86


Other scenarios found on the scenario status 
page, planned for 
Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to 
deployment or HC failures.
In addition, the following projects will be providing artifacts for the Hunter 
release:
Apex

Barometer

Bottlenecks

C-RAN

Calipso

Clover

Container4NFV

Doctor

Edge Cloud

FDS

Fuel

Functest

High Availability

IPv6

NFVBench

OPNFVDOC

OVN4NFV

SampleVNF

SFC

SNAPS-OO

Stor4NFV

StorPerf

VSPerf

Yardstick


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 (#23116): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23116
Mute This Topic: https://lists.opnfv.org/mt/31547970/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter=2783016
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-