On 08/12, Matt Darcy wrote: > That's really wise feedback and appreciated. > > I think I'll try to pull a proper feature request for this, as I've hit two > or three solid requirements for this now and it was used as a negative > against using foreman. > > Thanks,
I pretty much agree it'd be very useful - can you open an issue on http://projects.theforeman.org/issues/ to keep track of it? > > Matt > > > On Thursday, 11 August 2016 07:37:35 UTC+1, Marek Hulán wrote: > > > > On Tuesday 09 of August 2016 08:22:38 Matt Darcy wrote: > > > I've been doing a little bit of POC work on foreman 1.11 with EC2 (not > > > bothered moving to 1.12 for this POC as it's not really version > > specific). > > > > > > when building/modifying a host the EC2 compute plugin pulls a list of > > > subnets assigned to the account/compute resource associated to the > > foreman > > > compute resource target. this is nice and simple to use, however some > > > recent experience of what is in essence quite a small AWS estate, 6 > > VPCs, > > > at 9 subnets each, this become quite scappy as the list of 54 IP > > subnets, > > > totally out of any order was presented to the support team and without > > any > > > meaningful information about the subnets removed some of the ease and > > > management selling points that using foreman for the project been built > > on. > > > > > > In the POC I started looking at the ability to pull not only the IP CIDR > > > blocks but the comment field associated with the CIDR blocks. > > > > > > My initial tests look like it's possible to get the info, and I'd > > imagine > > > it's not too hard to create a second display box next to the IP list to > > > list the comments, or include a second field in the single box, but I'm > > > nowhere near that yet > > > > > > I thought I'd open up a short discussion (hopefully) about this as a > > > feature request and see if there is anything I've not considered > > > implication wise or anything I'd not seen the bigger picture on before > > > raising the feature request and looking to work on it and gather some > > > people to work on it. > > > > > > I'm currently looking at foreman for a much bigger EC2 deployment, which > > > will have many more subnets and without something human readable it will > > be > > > a much harder sell to use going forward. > > > > > > thoughts ? > > > > > > Matt > > > > Hello > > > > that sounds as a good addition to me. I'd prefer combining into a single > > select box, the second one would be hard to get in sync. I can imagine the > > comment being too long so some trimming might be considered. > > > > -- > > Marek > > > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
