Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Thanks, let me review the docs and see if I can map to the input file params. I 
need this to be scripted so I can repeat it as an automated process, similar to 
how CI/CD works. So I need to know the details of what the fields mean, 
mandatory/optional, and how to set them.

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 25, 2017 6:03 AM
To: SULLIVAN, BRYAN L <bs3...@att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,

You could use Fuel UI to avoid editing of yaml files:
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html
Anyway change of every value is not required.
Usually network settings are modified (i.e. interfaces, networks, vlan range, 
ips & etc.).
In most cases this is enough.

http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html

On Tue, Jan 24, 2017 at 10:17 PM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Is there anyone on the FUEL team monitoring this list? Really, we cannot make 
progress in Danube on Fuel support unless we get some basic support on the 
issues we have with standing up a Fuel-based deploy for testing.

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, January 19, 2017 2:44 PM
To: Michael Polenchuk <mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Resending, as I have not yet see a clarification of the fields in the 
dea-pod-override.yaml and dha.yaml files. I need this in order to setup our 
PODs to test under Fuel for the Copper, Models, and VES project.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, January 12, 2017 6:13 AM
To: 'Michael Polenchuk' 
<mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Michael,

We figured out that much after actually looking at the README file, but the 
details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how 
they should be setup for a specific POD, what are the options and values, 
what’s mandatory/optional, etc. In the repo, it looks like they refer to 
virtual envs, but after looking at the “secret” lab config versions it’s not 
much clearer. There are dozens of fields, subnet specs, etc and it’s unclear 
what they all related to. Where is the spec for all that?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 11:35 PM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?



On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?


Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the 
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well 
(.../opnfv-fuel/deploy/scenario).

--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.



--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[Michael Polenchuk]

Hi Bryan,

You could use Fuel UI to avoid editing of yaml files:
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html

Anyway change of every value is not required.
Usually network settings are modified (i.e. interfaces, networks, vlan
range, ips & etc.).
In most cases this is enough.

http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html


On Tue, Jan 24, 2017 at 10:17 PM, SULLIVAN, BRYAN L <bs3...@att.com> wrote:

> Is there anyone on the FUEL team monitoring this list? Really, we cannot
> make progress in Danube on Fuel support unless we get some basic support on
> the issues we have with standing up a Fuel-based deploy for testing.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *SULLIVAN,
> BRYAN L
> *Sent:* Thursday, January 19, 2017 2:44 PM
> *To:* Michael Polenchuk <mpolenc...@mirantis.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test
> in labs?
>
>
>
> Resending, as I have not yet see a clarification of the fields in the
> dea-pod-override.yaml and dha.yaml files. I need this in order to setup our
> PODs to test under Fuel for the Copper, Models, and VES project.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* SULLIVAN, BRYAN L
> *Sent:* Thursday, January 12, 2017 6:13 AM
> *To:* 'Michael Polenchuk' <mpolenc...@mirantis.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test
> in labs?
>
>
>
> Hi Michael,
>
>
>
> We figured out that much after actually looking at the README file, but
> the details of the dea-pod-override.yaml and dha.yaml files are unclear,
> i.e. how they should be setup for a specific POD, what are the options and
> values, what’s mandatory/optional, etc. In the repo, it looks like they
> refer to virtual envs, but after looking at the “secret” lab config
> versions it’s not much clearer. There are dozens of fields, subnet specs,
> etc and it’s unclear what they all related to. Where is the spec for all
> that?
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> <mpolenc...@mirantis.com>]
> *Sent:* Wednesday, January 11, 2017 11:35 PM
> *To:* SULLIVAN, BRYAN L <bs3...@att.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test
> in labs?
>
>
>
>
>
>
>
> On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L <bs3...@att.com> wrote:
>
> Thanks for the help here and on IRC – much appreciated.
>
> One other question as asked on IRC: The deploy.sh script requires a "-b
> base-uri" parameter which is the "stack-configuration" location. But there
> is no spec of what needs to be at that location/resource (I’m assuming this
> is an input, not output) - at least I can't find it. Any guidance?
>
>
>
>
>
> Hi Bryan,
>
> "-b base-uri" parameter usually pointed to the config which resides in the
> repo, e.g.:
> # git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel
>
> In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
> -s option is for a scenario name which is available in the repo as well
> (.../opnfv-fuel/deploy/scenario).
>
>
> --
>
>   Michael Polenchuk
>   Private Cloud / Mirantis Inc.
>



-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Is there anyone on the FUEL team monitoring this list? Really, we cannot make 
progress in Danube on Fuel support unless we get some basic support on the 
issues we have with standing up a Fuel-based deploy for testing.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Thursday, January 19, 2017 2:44 PM
To: Michael Polenchuk <mpolenc...@mirantis.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Resending, as I have not yet see a clarification of the fields in the 
dea-pod-override.yaml and dha.yaml files. I need this in order to setup our 
PODs to test under Fuel for the Copper, Models, and VES project.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, January 12, 2017 6:13 AM
To: 'Michael Polenchuk' 
<mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Michael,

We figured out that much after actually looking at the README file, but the 
details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how 
they should be setup for a specific POD, what are the options and values, 
what’s mandatory/optional, etc. In the repo, it looks like they refer to 
virtual envs, but after looking at the “secret” lab config versions it’s not 
much clearer. There are dozens of fields, subnet specs, etc and it’s unclear 
what they all related to. Where is the spec for all that?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 11:35 PM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?



On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?


Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the 
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well 
(.../opnfv-fuel/deploy/scenario).

--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Resending, as I have not yet see a clarification of the fields in the 
dea-pod-override.yaml and dha.yaml files. I need this in order to setup our 
PODs to test under Fuel for the Copper, Models, and VES project.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, January 12, 2017 6:13 AM
To: 'Michael Polenchuk' <mpolenc...@mirantis.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Michael,

We figured out that much after actually looking at the README file, but the 
details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how 
they should be setup for a specific POD, what are the options and values, 
what’s mandatory/optional, etc. In the repo, it looks like they refer to 
virtual envs, but after looking at the “secret” lab config versions it’s not 
much clearer. There are dozens of fields, subnet specs, etc and it’s unclear 
what they all related to. Where is the spec for all that?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 11:35 PM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?



On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?


Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the 
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well 
(.../opnfv-fuel/deploy/scenario).

--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Hi Michael,

We figured out that much after actually looking at the README file, but the 
details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how 
they should be setup for a specific POD, what are the options and values, 
what’s mandatory/optional, etc. In the repo, it looks like they refer to 
virtual envs, but after looking at the “secret” lab config versions it’s not 
much clearer. There are dozens of fields, subnet specs, etc and it’s unclear 
what they all related to. Where is the spec for all that?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 11:35 PM
To: SULLIVAN, BRYAN L <bs3...@att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?



On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?


Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the 
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well 
(.../opnfv-fuel/deploy/scenario).

--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[Michael Polenchuk]

On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L  wrote:

> Thanks for the help here and on IRC – much appreciated.
>
> One other question as asked on IRC: The deploy.sh script requires a "-b
> base-uri" parameter which is the "stack-configuration" location. But there
> is no spec of what needs to be at that location/resource (I’m assuming this
> is an input, not output) - at least I can't find it. Any guidance?
>
>
>
>
> Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well
(.../opnfv-fuel/deploy/scenario).

-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 8:03 AM
To: SULLIVAN, BRYAN L <bs3...@att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,
Please see answers inline ...


Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)
As I know nothing significant has changed in terms of installation procedure.

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo
Please refer at 
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103969.html

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc
This could be either virtual or baremetal (min RAM is ~2Gb, recommended 3Gb+ 
for fuel master node)

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM
deploy.sh script will do a trick (only thing is needed to install missing 
packages), it'll create all of vms, boot them ... and finally deploy a cluster 
as well:
opnfv-fuel/ci# ./deploy.sh -b file:///tmp/opnfv-fuel/deploy/config -l 
devel-pipeline -p default -s no-ha_nfv-ovs_heat_ceilometer_scenario.yaml -i 
file:///tmp/opnfv.iso

ready-to-use ISO you could get at 
http://artifacts.opnfv.org/fuel/latest.properties (OPNFV_ARTIFACT_URL=)

-  If supported, what are the minimum requirements for virtual deploy
RAM 10-11Gb for controllers, ram of computes depends on required workloads 
(1Gb+)

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work
The same as above.


--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[Michael Polenchuk]

Hi Bryan,

Please see answers inline ...


>
> Thanks for the link. I do look at the Jenkins status for high-level info,
> but it’s hard to find out the things I need from that, which are, to start
> related to how a developer deploys a simple fuel-based scenario (e.g.
> os-nosdn-nonha) in the lab
>
> -  What has changed since http://artifacts.opnfv.org/
> fuel/colorado/3.0/docs/installationprocedure/index.html (in general are
> there any draft Danube docs yet)
>
As I know nothing significant has changed in terms of installation
procedure.

> -  Is booting the fuel ISO the only option, or as with other
> installers can we build/deploy on the fly with a simple bash script
> (deploy.sh) after cloning the repo
>
Please refer at
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103969.html

> -  If booting the fuel ISO is the only option, what are the
> requirements for the jumphost, e.g. can this be done in a virt-manager VM
> (and how) or does it need to be bare metal, what are the host requirements
> (minimum) for the jumphost, etc
>
This could be either virtual or baremetal (min RAM is ~2Gb, recommended
3Gb+ for fuel master node)

> -  How is virtual deployment of the fuel master achieved (the
> install doc above does not specify the details) – it’s not clear if this is
> different from booting the fuel ISO in a VM
>
deploy.sh script will do a trick (only thing is needed to install missing
packages), it'll create all of vms, boot them ... and finally deploy a
cluster as well:
opnfv-fuel/ci# ./deploy.sh -b file:///tmp/opnfv-fuel/deploy/config -l
devel-pipeline -p default -s no-ha_nfv-ovs_heat_ceilometer_scenario.yaml -i
file:///tmp/opnfv.iso

ready-to-use ISO you could get at
http://artifacts.opnfv.org/fuel/latest.properties (OPNFV_ARTIFACT_URL=)

> -  If supported, what are the minimum requirements for virtual
> deploy
>
RAM 10-11Gb for controllers, ram of computes depends on required workloads
(1Gb+)

> -  What are the minimum requirements for bare metal lab servers,
> e.g. as I have been using will this work
>
The same as above.


-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Hi Fuel team,

Sorry to pester, but I didn’t get a response to this set of questions yet here 
or on IRC (#opnfv-fuel), so I’m pinging you again for help. With the short time 
until Danube freeze, we really need your help with Fuel install questions as 
below.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Tuesday, January 10, 2017 9:58 AM
To: Serg Melikyan <smelik...@mirantis.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM

-  If supported, what are the minimum requirements for virtual deploy

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work

o   Three Intel NUC i7 machines with two NICs, wake-on-lan + PXE boot (no 
IPMI), 16GB memory

Thanks,
Bryan Sullivan | AT

From: Serg Melikyan [mailto:smelik...@mirantis.com]
Sent: Tuesday, January 10, 2017 7:59 AM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,

indeed IRC channel mentioned on our wiki page was wrong, I have updated wiki 
page - our actively used IRC channel is #opnfv-fuel.

You can track our CI by the following link: 
http://build.opnfv.org/ci/view/fuel/ which has corresponding jobs for master 
which is Denube right now.

On Tue, Jan 10, 2017 at 7:20 AM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Hi all Fuel team members,

I’m looking for some guidance on how to track Fuel status for Danube and how to 
contact the Fuel team other than email, which we all have too much of. I see 
some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but it seems that 
the irc channel referenced (opnfv-bgs) has been idle for a while, so that’s 
clearly not where the OPNFV Fuel team hangs out.

But the basic question is whether Fuel is ready for Danube testing, e.g. has 
been updated to OpenStack Newton. The Copper project would like to help in the 
testing of Congress, and for Models and VES I want to start 
developing/verifying support under Fuel-based installs.

Please let me know where you guys hang out on IRC, Slack, Trello, or whatever, 
if we can start testing Fuel for Danube yet, and how to track the status of 
Fuel for Danube overall.

Thanks,
Bryan Sullivan | AT


___
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



--
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com<http://mirantis.com/> | 
smelik...@mirantis.com<mailto:smelik...@mirantis.com> | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM

-  If supported, what are the minimum requirements for virtual deploy

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work

o   Three Intel NUC i7 machines with two NICs, wake-on-lan + PXE boot (no 
IPMI), 16GB memory

Thanks,
Bryan Sullivan | AT

From: Serg Melikyan [mailto:smelik...@mirantis.com]
Sent: Tuesday, January 10, 2017 7:59 AM
To: SULLIVAN, BRYAN L <bs3...@att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,

indeed IRC channel mentioned on our wiki page was wrong, I have updated wiki 
page - our actively used IRC channel is #opnfv-fuel.

You can track our CI by the following link: 
http://build.opnfv.org/ci/view/fuel/ which has corresponding jobs for master 
which is Denube right now.

On Tue, Jan 10, 2017 at 7:20 AM, SULLIVAN, BRYAN L 
<bs3...@att.com<mailto:bs3...@att.com>> wrote:
Hi all Fuel team members,

I’m looking for some guidance on how to track Fuel status for Danube and how to 
contact the Fuel team other than email, which we all have too much of. I see 
some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but it seems that 
the irc channel referenced (opnfv-bgs) has been idle for a while, so that’s 
clearly not where the OPNFV Fuel team hangs out.

But the basic question is whether Fuel is ready for Danube testing, e.g. has 
been updated to OpenStack Newton. The Copper project would like to help in the 
testing of Congress, and for Models and VES I want to start 
developing/verifying support under Fuel-based installs.

Please let me know where you guys hang out on IRC, Slack, Trello, or whatever, 
if we can start testing Fuel for Danube yet, and how to track the status of 
Fuel for Danube overall.

Thanks,
Bryan Sullivan | AT


___
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



--
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com<http://mirantis.com/> | 
smelik...@mirantis.com<mailto:smelik...@mirantis.com> | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[Serg Melikyan]

Hi Bryan,

indeed IRC channel mentioned on our wiki page was wrong, I have updated
wiki page - our actively used IRC channel is #opnfv-fuel.

You can track our CI by the following link:
http://build.opnfv.org/ci/view/fuel/ which has corresponding jobs for
master which is Denube right now.

On Tue, Jan 10, 2017 at 7:20 AM, SULLIVAN, BRYAN L  wrote:

> Hi all Fuel team members,
>
>
>
> I’m looking for some guidance on how to track Fuel status for Danube and
> how to contact the Fuel team other than email, which we all have too much
> of. I see some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but
> it seems that the irc channel referenced (opnfv-bgs) has been idle for a
> while, so that’s clearly not where the OPNFV Fuel team hangs out.
>
>
>
> But the basic question is whether Fuel is ready for Danube testing, e.g.
> has been updated to OpenStack Newton. The Copper project would like to help
> in the testing of Congress, and for Models and VES I want to start
> developing/verifying support under Fuel-based installs.
>
>
>
> Please let me know where you guys hang out on IRC, Slack, Trello, or
> whatever, if we can start testing Fuel for Danube yet, and how to track the
> status of Fuel for Danube overall.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss