Is anyone against relaxing the restriction against duplicate host names? What if the unique restriction was enforced at the organization level?
In addition to multi-tenant needs, there is also a case where customers need to have hosts be represented from a subscription point of view differently depending on the organization. Specifically, a hypervisor is often "duplicated" in multiple organizations so that different product subscriptions may be assigned for the groups.
···
--
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself apart form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle
“Leadership is about making others better as a result of your presence and making sure that impact lasts in your absence.” ~ Harvard Business School
Given the fluid nature of our hosts being passed from org to org, I would
not want to deal with the conflicts that may arise.
···
On Monday, October 12, 2015 at 7:45:49 AM UTC-5, Tom McKay wrote:
>
>
> Is anyone against relaxing the restriction against duplicate host names?
> What if the unique restriction was enforced at the organization level?
>
> In addition to multi-tenant needs, there is also a case where customers
> need to have hosts be represented from a subscription point of view
> differently depending on the organization. Specifically, a hypervisor is
> often "duplicated" in multiple organizations so that different product
> subscriptions may be assigned for the groups.
>
>
> --
> @thomasmckay
>
> --
> "The leader must aim high, see big, judge widely, thus setting himself
> apart form the ordinary people who debate in narrow confines." ~ Charles De
> Gaulle
>
> "Leadership is about making others better as a result of your presence and
> making sure that impact lasts in your absence." ~ Harvard Business School
>
I don't think this is possible with puppet - perhaps hypervisor should be
an aspect?
···
On Oct 12, 2015 2:45 PM, "Tom McKay" wrote:
Is anyone against relaxing the restriction against duplicate host names?
What if the unique restriction was enforced at the organization level?
In addition to multi-tenant needs, there is also a case where customers
need to have hosts be represented from a subscription point of view
differently depending on the organization. Specifically, a hypervisor is
often “duplicated” in multiple organizations so that different product
subscriptions may be assigned for the groups.
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
Is anyone against relaxing the restriction against duplicate host names?
What if the unique restriction was enforced at the organization level?
In addition to multi-tenant needs, there is also a case where customers
need to have hosts be represented from a subscription point of view
differently depending on the organization. Specifically, a hypervisor is
often “duplicated” in multiple organizations so that different product
subscriptions may be assigned for the groups.
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
Is anyone against relaxing the restriction against duplicate host names?
What if the unique restriction was enforced at the organization level?
In addition to multi-tenant needs, there is also a case where customers
need to have hosts be represented from a subscription point of view
differently depending on the organization. Specifically, a hypervisor is
often “duplicated” in multiple organizations so that different product
subscriptions may be assigned for the groups.
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
> Given the fluid nature of our hosts being passed from org to org, I would
> not want to deal with the conflicts that may arise.
Would there be conflicts if your usage never created same-named hosts? What conflicts do you envision for your usage? Are there times when the duplicate name validation has prevented error scenarios?
Lots of questions, I know.
···
----- Original Message -----
On Monday, October 12, 2015 at 7:45:49 AM UTC-5, Tom McKay wrote:
Is anyone against relaxing the restriction against duplicate host names?
What if the unique restriction was enforced at the organization level?
In addition to multi-tenant needs, there is also a case where customers
need to have hosts be represented from a subscription point of view
differently depending on the organization. Specifically, a hypervisor is
often “duplicated” in multiple organizations so that different product
subscriptions may be assigned for the groups.
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
We are on track to bring on 20+ orgs by years end and I already see
'jenkins', 'www', 'test', 'foo' hostname variations.
Multiple orgs working on a similar project will pass a host to another
org rather than add users into their org.
···
On Tuesday, October 13, 2015 at 5:12:48 PM UTC-5, Tom McKay wrote:
>
>
>
> ----- Original Message -----
> > Given the fluid nature of our hosts being passed from org to org, I
> would
> > not want to deal with the conflicts that may arise.
>
> Would there be conflicts if your usage never created same-named hosts?
> What conflicts do you envision for your usage? Are there times when the
> duplicate name validation has prevented error scenarios?
>
> Lots of questions, I know. :)
>
>
>
