I ran into issues/confusion creating a new host in foretello and am trying to determine what the intended correct behavior is supposed to be. Depending on the answers below, it seems there are some big gaps in how the UI validates objects during creation and use.
True or false?
In foretello, organizations and locations are required to be enabled.
Organization nesting is forced disabled.
Location nesting is forced enabled.
All foreman resources are required to belong to an organization.
All katello resources are required to belong to an organization.
All foreman resources are required to belong to a location.
All katello resources are required to belong to a location.
Resources, be they foreman or katello, may only belong to one and only one organization.
Resources, be they foreman or katello, may only belong to one and only one location.
···
--
@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 ran into issues/confusion creating a new host in foretello and am
trying to determine what the intended correct behavior is supposed to be.
Depending on the answers below, it seems there are some big gaps in how the
UI validates objects during creation and use.
>
> True or false?
>
> 1. In foretello, organizations and locations are required to be enabled.
IMHO false, but its not a bad idea to be the default.
>
> 2. Organization nesting is forced disabled.
True for the first version ( or until katello adds support for it).
>
> 3. Location nesting is forced enabled.
Not forced, but it's a feature added part 1.4.
>
> 4. All foreman resources are required to belong to an organization.
False most but not all, some are indirectly assign - reports facts etc.
Others not implemented - audits some are global - roles
>
> 5. All katello resources are required to belong to an organization.
>
> 6. All foreman resources are required to belong to a location.
Same as #4 (assuming its enable as in #1)
>
> 7. All katello resources are required to belong to a location.
I don't think katello is aware of the location currently.
>
> 8. Resources, be they foreman or katello, may only belong to one and only
one organization.
False, true only for hosts
>
> 9. Resources, be they foreman or katello, may only belong to one and only
one location.
>
Same as #8
>
>
> –
> @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
>
> –
> You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
···
On Mar 30, 2014 6:20 PM, "Tom McKay" wrote:
> For more options, visit https://groups.google.com/d/optout.
>
> >
> >
> > I ran into issues/confusion creating a new host in foretello and am
> trying to determine what the intended correct behavior is supposed to
> be. Depending on the answers below, it seems there are some big gaps in
> how the UI validates objects during creation and use.
> >
> > True or false?
> >
> > 1. In foretello, organizations and locations are required to be
> enabled.
> IMHO false, but its not a bad idea to be the default.
Today I think true, long term… we should discuss but I would suggest false.
> >
> > 2. Organization nesting is forced disabled.
> True for the first version ( or until katello adds support for it).
trye
> >
> > 3. Location nesting is forced enabled.
> Not forced, but it's a feature added part 1.4.
true
> >
> > 4. All foreman resources are required to belong to an organization.
> False most but not all, some are indirectly assign - reports facts etc.
> Others not implemented - audits some are global - roles
> >
> > 5. All katello resources are required to belong to an organization.
> >
true
> > 6. All foreman resources are required to belong to a location.
> Same as #4 (assuming its enable as in #1)
> >
> > 7. All katello resources are required to belong to a location.
> I don't think katello is aware of the location currently.
> >
> > 8. Resources, be they foreman or katello, may only belong to one and
> only one organization.
>
> False, true only for hosts
> >
> > 9. Resources, be they foreman or katello, may only belong to one and
> only one location.
> >
> Same as #8
> >
I think what you are seeing here is that katello assumed strict
tenancy… where foreman did not. I tend to think long term we may want
to look more to foreamns model… but that will require changing katello,
candlepin, and possibly pulp.
bk
···
On 03/30/2014 04:05 PM, Ohad Levy wrote:
> On Mar 30, 2014 6:20 PM, "Tom McKay" > wrote:
My issue/confusion is that creating a host required the selection of a location, yet not all of the resources required to specify with the org required a location. Which is correct, all resources must have a location or it's optional? If a host must have a location, and the other resources entire purpose is for hosts to use, why would any resource not also require that at least one location be specified? There's a disconnect there, right?
···
----- Original Message -----
> Comments below
>
> On 03/30/2014 04:05 PM, Ohad Levy wrote:
> >
> > On Mar 30, 2014 6:20 PM, "Tom McKay" > > wrote:
> > >
> > >
> > > I ran into issues/confusion creating a new host in foretello and am
> > trying to determine what the intended correct behavior is supposed to
> > be. Depending on the answers below, it seems there are some big gaps in
> > how the UI validates objects during creation and use.
> > >
> > > True or false?
> > >
> > > 1. In foretello, organizations and locations are _required_ to be
> > enabled.
> > IMHO false, but its not a bad idea to be the default.
>
> Today I think true, long term.. we should discuss but I would suggest false.
>
>
> > >
> > > 2. Organization nesting is forced disabled.
> > True for the first version ( or until katello adds support for it).
>
> trye
>
> > >
> > > 3. Location nesting is forced enabled.
> > Not forced, but it's a feature added part 1.4.
>
> true
>
> > >
> > > 4. All foreman resources are required to belong to an organization.
> > False most but not all, some are indirectly assign - reports facts etc.
> > Others not implemented - audits some are global - roles
> > >
> > > 5. All katello resources are required to belong to an organization.
> > >
>
> true
>
> > > 6. All foreman resources are required to belong to a location.
> > Same as #4 (assuming its enable as in #1)
> > >
> > > 7. All katello resources are required to belong to a location.
> > I don't think katello is aware of the location currently.
> > >
> > > 8. Resources, be they foreman or katello, may only belong to one and
> > only one organization.
> >
> > False, true only for hosts
> > >
> > > 9. Resources, be they foreman or katello, may only belong to one and
> > only one location.
> > >
> > Same as #8
> > >
>
>
> I think what you are seeing here is that katello assumed strict
> tenancy.. where foreman did not. I tend to think long term we may want
> to look more to foreamns model.. but that will require changing katello,
> candlepin, and possibly pulp.
>
> - bk
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
I'm not sure locations should be on by default, as it probably
is not the key feature, but adds a lot of additional steps
to be able to start provisioning (since once enabled, you can't
create a host without location enabled).
The fix for me would be either fixing #4712 and making the locations
disabled by default or creating a "default location", not scoping
anything: just to make foreman happy, when I really don't care about locations.
– Ivan
···
----- Original Message -----
>
>
> ----- Original Message -----
> > Comments below
> >
> > On 03/30/2014 04:05 PM, Ohad Levy wrote:
> > >
> > > On Mar 30, 2014 6:20 PM, "Tom McKay" > > > wrote:
> > > >
> > > >
> > > > I ran into issues/confusion creating a new host in foretello and am
> > > trying to determine what the intended correct behavior is supposed to
> > > be. Depending on the answers below, it seems there are some big gaps in
> > > how the UI validates objects during creation and use.
> > > >
> > > > True or false?
> > > >
> > > > 1. In foretello, organizations and locations are _required_ to be
> > > enabled.
> > > IMHO false, but its not a bad idea to be the default.
> >
> > Today I think true, long term.. we should discuss but I would suggest
> > false.
> >
> >
> > > >
> > > > 2. Organization nesting is forced disabled.
> > > True for the first version ( or until katello adds support for it).
> >
> > trye
> >
> > > >
> > > > 3. Location nesting is forced enabled.
> > > Not forced, but it's a feature added part 1.4.
> >
> > true
> >
> > > >
> > > > 4. All foreman resources are required to belong to an organization.
> > > False most but not all, some are indirectly assign - reports facts etc.
> > > Others not implemented - audits some are global - roles
> > > >
> > > > 5. All katello resources are required to belong to an organization.
> > > >
> >
> > true
> >
> > > > 6. All foreman resources are required to belong to a location.
> > > Same as #4 (assuming its enable as in #1)
> > > >
> > > > 7. All katello resources are required to belong to a location.
> > > I don't think katello is aware of the location currently.
> > > >
> > > > 8. Resources, be they foreman or katello, may only belong to one and
> > > only one organization.
> > >
> > > False, true only for hosts
> > > >
> > > > 9. Resources, be they foreman or katello, may only belong to one and
> > > only one location.
> > > >
> > > Same as #8
> > > >
> >
> >
> > I think what you are seeing here is that katello assumed strict
> > tenancy.. where foreman did not. I tend to think long term we may want
> > to look more to foreamns model.. but that will require changing katello,
> > candlepin, and possibly pulp.
> >
> > - bk
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "foreman-dev" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to foreman-dev+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> My issue/confusion is that creating a host required the selection of a
> location, yet not all of the resources required to specify with the org
> required a location. Which is correct, all resources must have a location or
> it's optional? If a host _must_ have a location, and the other resources
> entire purpose is for hosts to use, why would any resource not also require
> that at least one location be specified? There's a disconnect there, right?
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
···
----- Original Message -----
> Enabling locations by default seems to be a consequence of this bug
> http://projects.theforeman.org/issues/4712
>
> I'm not sure locations should be on by default, as it probably
> is not the key feature, but adds a lot of additional steps
> to be able to start provisioning (since once enabled, you can't
> create a host without location enabled).
>
> The fix for me would be either fixing #4712 and making the locations
> disabled by default or creating a "default location", not scoping
> anything: just to make foreman happy, when I really don't care about
> locations.
>
> -- Ivan
>
> ----- Original Message -----
> >
> >
> > ----- Original Message -----
> > > Comments below
> > >
> > > On 03/30/2014 04:05 PM, Ohad Levy wrote:
> > > >
> > > > On Mar 30, 2014 6:20 PM, "Tom McKay" > > > > wrote:
> > > > >
> > > > >
> > > > > I ran into issues/confusion creating a new host in foretello and am
> > > > trying to determine what the intended correct behavior is supposed to
> > > > be. Depending on the answers below, it seems there are some big gaps in
> > > > how the UI validates objects during creation and use.
> > > > >
> > > > > True or false?
> > > > >
> > > > > 1. In foretello, organizations and locations are _required_ to be
> > > > enabled.
> > > > IMHO false, but its not a bad idea to be the default.
> > >
> > > Today I think true, long term.. we should discuss but I would suggest
> > > false.
> > >
> > >
> > > > >
> > > > > 2. Organization nesting is forced disabled.
> > > > True for the first version ( or until katello adds support for it).
> > >
> > > trye
> > >
> > > > >
> > > > > 3. Location nesting is forced enabled.
> > > > Not forced, but it's a feature added part 1.4.
> > >
> > > true
> > >
> > > > >
> > > > > 4. All foreman resources are required to belong to an organization.
> > > > False most but not all, some are indirectly assign - reports facts etc.
> > > > Others not implemented - audits some are global - roles
> > > > >
> > > > > 5. All katello resources are required to belong to an organization.
> > > > >
> > >
> > > true
> > >
> > > > > 6. All foreman resources are required to belong to a location.
> > > > Same as #4 (assuming its enable as in #1)
> > > > >
> > > > > 7. All katello resources are required to belong to a location.
> > > > I don't think katello is aware of the location currently.
> > > > >
> > > > > 8. Resources, be they foreman or katello, may only belong to one and
> > > > only one organization.
> > > >
> > > > False, true only for hosts
> > > > >
> > > > > 9. Resources, be they foreman or katello, may only belong to one and
> > > > only one location.
> > > > >
> > > > Same as #8
> > > > >
> > >
> > >
> > > I think what you are seeing here is that katello assumed strict
> > > tenancy.. where foreman did not. I tend to think long term we may want
> > > to look more to foreamns model.. but that will require changing katello,
> > > candlepin, and possibly pulp.
> > >
> > > - bk
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "foreman-dev" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an
> > > email to foreman-dev+unsubscribe@googlegroups.com.
> > > For more options, visit https://groups.google.com/d/optout.
> > >
> >
> > My issue/confusion is that creating a host required the selection of a
> > location, yet not all of the resources required to specify with the org
> > required a location. Which is correct, all resources must have a location
> > or
> > it's optional? If a host _must_ have a location, and the other resources
> > entire purpose is for hosts to use, why would any resource not also require
> > that at least one location be specified? There's a disconnect there, right?
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "foreman-dev" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to foreman-dev+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
···
On 03/31/2014 11:53 AM, Ivan Necas wrote:
> I've filed an issue against that
>
> http://projects.theforeman.org/issues/4975
>
> -- Ivan
>
> ----- Original Message -----
>> Enabling locations by default seems to be a consequence of this bug
>> http://projects.theforeman.org/issues/4712
>>
>> I'm not sure locations should be on by default, as it probably
>> is not the key feature, but adds a lot of additional steps
>> to be able to start provisioning (since once enabled, you can't
>> create a host without location enabled).
>>
>> The fix for me would be either fixing #4712 and making the locations
>> disabled by default or creating a "default location", not scoping
>> anything: just to make foreman happy, when I really don't care about
>> locations.
>>
>> -- Ivan
>>
>> ----- Original Message -----
>>>
>>>
>>> ----- Original Message -----
>>>> Comments below
>>>>
>>>> On 03/30/2014 04:05 PM, Ohad Levy wrote:
>>>>>
>>>>> On Mar 30, 2014 6:20 PM, "Tom McKay" >>>> > wrote:
>>>>> >
>>>>> >
>>>>> > I ran into issues/confusion creating a new host in foretello and am
>>>>> trying to determine what the intended correct behavior is supposed to
>>>>> be. Depending on the answers below, it seems there are some big gaps in
>>>>> how the UI validates objects during creation and use.
>>>>> >
>>>>> > True or false?
>>>>> >
>>>>> > 1. In foretello, organizations and locations are _required_ to be
>>>>> enabled.
>>>>> IMHO false, but its not a bad idea to be the default.
>>>>
>>>> Today I think true, long term.. we should discuss but I would suggest
>>>> false.
>>>>
>>>>
>>>>> >
>>>>> > 2. Organization nesting is forced disabled.
>>>>> True for the first version ( or until katello adds support for it).
>>>>
>>>> trye
>>>>
>>>>> >
>>>>> > 3. Location nesting is forced enabled.
>>>>> Not forced, but it's a feature added part 1.4.
>>>>
>>>> true
>>>>
>>>>> >
>>>>> > 4. All foreman resources are required to belong to an organization.
>>>>> False most but not all, some are indirectly assign - reports facts etc.
>>>>> Others not implemented - audits some are global - roles
>>>>> >
>>>>> > 5. All katello resources are required to belong to an organization.
>>>>> >
>>>>
>>>> true
>>>>
>>>>> > 6. All foreman resources are required to belong to a location.
>>>>> Same as #4 (assuming its enable as in #1)
>>>>> >
>>>>> > 7. All katello resources are required to belong to a location.
>>>>> I don't think katello is aware of the location currently.
>>>>> >
>>>>> > 8. Resources, be they foreman or katello, may only belong to one and
>>>>> only one organization.
>>>>>
>>>>> False, true only for hosts
>>>>> >
>>>>> > 9. Resources, be they foreman or katello, may only belong to one and
>>>>> only one location.
>>>>> >
>>>>> Same as #8
>>>>> >
>>>>
>>>>
>>>> I think what you are seeing here is that katello assumed strict
>>>> tenancy.. where foreman did not. I tend to think long term we may want
>>>> to look more to foreamns model.. but that will require changing katello,
>>>> candlepin, and possibly pulp.
>>>>
>>>> - bk
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "foreman-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an
>>>> email to foreman-dev+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> My issue/confusion is that creating a host required the selection of a
>>> location, yet not all of the resources required to specify with the org
>>> required a location. Which is correct, all resources must have a location
>>> or
>>> it's optional? If a host _must_ have a location, and the other resources
>>> entire purpose is for hosts to use, why would any resource not also require
>>> that at least one location be specified? There's a disconnect there, right?
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "foreman-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to foreman-dev+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-dev+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
