Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1455163

Summary: Hosted-Engine installer should ask the name of the Data Center that will be created
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Yaniv Kaul <ykaul>
Component: RFEsAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: low    
Version: 2.1.0.6CC: bugs, sbonazzo, ykaul, ylavi
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: ---Flags: ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-19 17:15:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2017-05-24 12:04:22 UTC
Description of problem:
The installer should ask for the name of the 1st DC (that will contain the HE SD) name. The default is of course 'Default'.

Comment 1 Sandro Bonazzola 2017-07-21 11:27:20 UTC
Did you mean cluster name or data center name?
Because cluster name is already asked and defaults to "Default" (see https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=src/plugins/gr-he-setup/engine/add_host.py;h=fdbb597ead807b978e24a075585ddb5b3a292b0c;hb=refs/heads/master#l503 )

while the data center name defaults to "hosted_datacenter"
see https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=src/ovirt_hosted_engine_setup/constants.py;h=1f9d46d230eaba8d8ada62095c85e1bcf9eef303;hb=refs/heads/master#l1071
but if I remember correctly, this is only used while initializing the HE disk.

As far as I can remember the installer is not creating the "Default" data center.

What's the purpose of this request?

Assigning to Simone who knows better than me this part.

Comment 2 Yaniv Kaul 2017-07-21 14:02:10 UTC
(In reply to Sandro Bonazzola from comment #1)
> Did you mean cluster name or data center name?
> Because cluster name is already asked and defaults to "Default" (see
> https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=src/
> plugins/gr-he-setup/engine/add_host.py;
> h=fdbb597ead807b978e24a075585ddb5b3a292b0c;hb=refs/heads/master#l503 )
> 
> while the data center name defaults to "hosted_datacenter"
> see
> https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=src/
> ovirt_hosted_engine_setup/constants.py;
> h=1f9d46d230eaba8d8ada62095c85e1bcf9eef303;hb=refs/heads/master#l1071
> but if I remember correctly, this is only used while initializing the HE
> disk.
> 
> As far as I can remember the installer is not creating the "Default" data
> center.
> 
> What's the purpose of this request?

We'd like to have the HE domain imported as part of the installation process (at the very end of it, via Ansible). To do so, I believe we must ask 2 questions: DC name and cluster name (with both having defaults)

> 
> Assigning to Simone who knows better than me this part.

Comment 3 Yaniv Kaul 2017-08-02 13:36:29 UTC
Yaniv L. - we need this in order to properly create the VM, via the REST API. This is part of the Hosted-engine new bootstrapping workflow.

Comment 4 Yaniv Lavi 2017-08-10 11:29:13 UTC
I don't understand why this is needed?
Why can you use the Default DC and cluster for this?

Comment 5 Yaniv Kaul 2017-08-11 07:56:56 UTC
(In reply to Yaniv Lavi (Dary) from comment #4)
> I don't understand why this is needed?
> Why can you use the Default DC and cluster for this?

These values should be the default answers for the questions.

Comment 6 Yaniv Lavi 2017-08-13 10:52:22 UTC
(In reply to Yaniv Kaul from comment #5)
> (In reply to Yaniv Lavi (Dary) from comment #4)
> > I don't understand why this is needed?
> > Why can you use the Default DC and cluster for this?
> 
> These values should be the default answers for the questions.

Why is it critical to ask this at all? These defaults exist in the setup even if they are not asked.

Comment 7 Yaniv Kaul 2017-08-13 11:07:23 UTC
(In reply to Yaniv Lavi (Dary) from comment #6)
> (In reply to Yaniv Kaul from comment #5)
> > (In reply to Yaniv Lavi (Dary) from comment #4)
> > > I don't understand why this is needed?
> > > Why can you use the Default DC and cluster for this?
> > 
> > These values should be the default answers for the questions.
> 
> Why is it critical to ask this at all? These defaults exist in the setup
> even if they are not asked.

Because customers ask for it to be configured. I'm not sure why we even have a discussion. It's a question, with a default.

Comment 8 Yaniv Lavi 2017-08-13 11:27:50 UTC
(In reply to Yaniv Kaul from comment #7)
> (In reply to Yaniv Lavi (Dary) from comment #6)
> > (In reply to Yaniv Kaul from comment #5)
> > > (In reply to Yaniv Lavi (Dary) from comment #4)
> > > > I don't understand why this is needed?
> > > > Why can you use the Default DC and cluster for this?
> > > 
> > > These values should be the default answers for the questions.
> > 
> > Why is it critical to ask this at all? These defaults exist in the setup
> > even if they are not asked.
> 
> Because customers ask for it to be configured. I'm not sure why we even have
> a discussion. It's a question, with a default.

Because the setup currently doesn't configure any DCs or cluster, so it more than just a question. I don't have any customer asking for this as well.

Comment 9 Sandro Bonazzola 2017-10-13 11:47:24 UTC
This will be handled as part of the node zero setup.

Comment 10 Yaniv Kaul 2017-11-16 14:29:47 UTC
Has it been implemented in the new wizard?

Comment 11 Sandro Bonazzola 2017-11-30 09:33:17 UTC
(In reply to Yaniv Kaul from comment #10)
> Has it been implemented in the new wizard?

Not yet

Comment 12 Simone Tiraboschi 2017-12-19 17:15:12 UTC

*** This bug has been marked as a duplicate of bug 1406067 ***