[sles-beta] Odd happenings in the register with RC2 to RC3 update
Waite, Dick (External)
Dick.Waite at softwareag.com
Fri Oct 30 01:45:39 MDT 2015
Grand New Friday People,
I updated some more of my QE systems to RC3 early today and these systems also pop back into the register with IP numbers and not node names (Hostname).
For me the NODE name tells me where it is and what it's function in life is. It's IP number tells me sweet BA and to be honest I don't want to know it.
So if this is the new feature of register with RC3 can I please have an option to have the RC2 and before method or put the code back as was.
Who wants to know what the IP number is, the NODE name tells the user / customer what the system does, the node can be switched onto other systems but it's function will not change, yes it's IP will but why does that matter. For me this is not a grand update. Not a happy chappy.
I would like to know from others who are running RC3 out there did this switch happen for you, is this a Halloween joke by the good people of SUSE. These were machines registered with RC2 running, when RC3 ran the register did have a chatter but did not ask if I wanted to re-register or de-register it just said fine I'll update the items you have ask for. The scripting modules is a must for us, life without PHP just does not work.
While on on I will ask why we can request updates to the SDK, and we also have the SDK attached as a 2nd DVD/iso, seem a sort of belt and braces, do we still need the SDK DVD/iso if we register we want the SDK?
Have you all a grand Halloween and I hope Hostname returns to the register on Monday, good joke SUSE ;o)
__R
Registered systems
Hostname Hardware Info Identifier
10.20.114.221 3 CPUs, 1 Socket, VMware, uuid 564d728f-2b61-7b49-7bfa-3b21c7696bf0, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550023>
10.20.115.18 3 CPUs, 1 Socket, VMware, uuid 564dd71a-2ce6-10dc-797d-393f64de4507, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550236>
10.20.115.5 3 CPUs, 1 Socket, VMware, uuid 564de523-be64-f70c-9cbf-a92580339efb, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550254>
192.168.2.110 2 CPUs, 1 Socket, VMware, uuid 564df181-114c-b3a2-617c-fa9821963999, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550702>
192.168.2.114 2 CPUs, 1 Socket, VMware, uuid 564d83e2-3dd0-6ed0-f7db-9cf6c51c947e, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550709>
192.168.2.124 3 CPUs, 1 Socket, VMware, uuid 564d5bdc-e03e-5224-fa15-977066e4b4b8, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549448>
192.168.2.127 4 CPUs, 1 Socket, VMware, uuid 564dfb54-4ba8-4625-ef03-612a1e397160, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1552269>
192.168.2.147 2 CPUs, 1 Socket, VMware, uuid 564d30df-4bab-b6ec-177c-ad24ea0947d0, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550683>
ACER-12-1-3 2 CPUs, 1 Socket, VMware, uuid 564ddf90-18c7-0c0f-ebe5-06d3fb9db36d, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549437>
rjw02-12-1-1 4 CPUs, 1 Socket, VMware, uuid 564d8cd2-a6b3-5151-6fa2-a5e4a9a339df, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549451>
rjw02-12-1-2 4 CPUs, 1 Socket, VMware, uuid 564d8cd2-a6b3-5151-6fa2-a5e4a9a339df, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549436>
rjw02-12-1-newi 3 CPUs, 1 Socket, VMware, uuid ef8d4d56-9905-cc51-6d76-dea8493557da, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549429>
rjw1-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564d6006-65fa-3383-24a5-d32fe30a3b01, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549162>
rjw3-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564db14a-5ebe-352c-1c2a-d40cac5033a8, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549991>
rjw3-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564de762-6094-3e7d-4b50-45d3855181e6, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550089>
rjw7-12-1-01 3 CPUs, 1 Socket, VMware, uuid 564d83b8-c621-4d3b-b8d2-0df68dba34fc, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549147>
________________________________
From: Waite, Dick (External)
Sent: 29 October 2015 19:00
To: sles-beta at lists.suse.com
Cc: Vincent Moutoussamy
Subject: Odd happenings in the register with RC2 to RC3 update
Grand Evening,
Spent some happy hours today updating a number of system from RC2 to RC3. Tried a number of ways and they all worked well, no issues on that front.
When a cast by eyeballs onto the browser showing ssc.suse.com... I see I'm not getting node names with RC3 but IP's and for example 192.168.2.127 is in fact rjw02-12-1-1. Should I now de-register the node, but I like node names.
I do think a node name is more helpful for me, but if giving us IP's and not node name is what SUSE want RC3 to give us ? or should I create an SR ? If an option on the SUSEConnect can say give node or IP that would be friendly, then if the customer likes nodes they get nodes or default IP's
Just as wondering minds like to know, how is the uuid created, from what parts of the system? If this is secret then we can continue to wonder.
SUSE Linux Enterprise Server 12 SP1 beta subscription
Hostname Hardware Info Identifier
192.168.2.110 2 CPUs, 1 Socket, VMware, uuid 564df181-114c-b3a2-617c-fa9821963999, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550702>
192.168.2.114 2 CPUs, 1 Socket, VMware, uuid 564d83e2-3dd0-6ed0-f7db-9cf6c51c947e, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550709>
192.168.2.124 3 CPUs, 1 Socket, VMware, uuid 564d5bdc-e03e-5224-fa15-977066e4b4b8, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549448>
192.168.2.127 4 CPUs, 1 Socket, VMware, uuid 564dfb54-4ba8-4625-ef03-612a1e397160, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1552269>
192.168.2.147 2 CPUs, 1 Socket, VMware, uuid 564d30df-4bab-b6ec-177c-ad24ea0947d0, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550683>
<https://scc.suse.com/subscriptions/2942687/systems/1549437>
rjw02-12-1-1 4 CPUs, 1 Socket, VMware, uuid 564d8cd2-a6b3-5151-6fa2-a5e4a9a339df, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549451>
rjw02-12-1-2 4 CPUs, 1 Socket, VMware, uuid 564d8cd2-a6b3-5151-6fa2-a5e4a9a339df, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549436>
rjw02-12-1-newi 3 CPUs, 1 Socket, VMware, uuid ef8d4d56-9905-cc51-6d76-dea8493557da, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549429>
rjw1-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564d6006-65fa-3383-24a5-d32fe30a3b01, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549162>
rjw3-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564db14a-5ebe-352c-1c2a-d40cac5033a8, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549991>
rjw3-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564de762-6094-3e7d-4b50-45d3855181e6, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550089>
rjw5-12-1-00 3 CPUs, 1 Socket, VMware, uuid 564de523-be64-f70c-9cbf-a92580339efb, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550254>
rjw5-12-1-01 3 CPUs, 1 Socket, VMware, uuid 564dd71a-2ce6-10dc-797d-393f64de4507, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550236>
rjw5-12-1-02 3 CPUs, 1 Socket, VMware, uuid 564d728f-2b61-7b49-7bfa-3b21c7696bf0, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1550023>
rjw7-12-1-01 3 CPUs, 1 Socket, VMware, uuid 564d83b8-c621-4d3b-b8d2-0df68dba34fc, arch: x86_64 unknown <https://scc.suse.com/subscriptions/2942687/systems/1549147>
Software AG – Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany – Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20151030/c464de1b/attachment.htm>
More information about the sles-beta
mailing list