HP-UX vPars Development Team Wants Your Feedback

[Patrice Le Guyader]

1)yes. 8 Npars on 3 RX/RP.
134 Vpars on 12 SD.
109 Npars on 34 SD.

2)Yes, a must.

3) All versions and I think it must not be specific to a release. A GUI like VCS Cluster manager.

4)Why not, It can be a possibility to learn how to manage the vpars/npars, if you can see what are the command launched really.

5)All basic administration tasks, advanced ones need to done with CLI.

6)Standalone, with a release on windows,linux. You can include a GUI light in SMH but a heavy standalone one stay for me the good idea.

a) VSE : No opinion perhaps a light GUI.
b) SMH : a light GUI.

7) No real challenge. Just to be sure I'm working on the good one. ;-)

[Turgay Cavdar]

1. Yes. 40 vpars on 6 server.

2. Yes, a must.(Because partition manager, HPVM all have GUIs.Why not for vpar?

3. All.

4. I don't prefer GUI.

5. Creation of new vpars, modification of vpars.

6. It should be integrated with SMH and HPSIM/VSE

7. Managing vpars from central point from HPSIM/VSE

[likid0]

1. Yes, 45 vpars, 4/5 vpars per npar
2. I never used it on 11.11, don't really think you need a gui, cli does a good job.
3 If you are going to do a gui, it would be be better to have in all versions posible.
4. I prefer cli, because in many of my servers I don't have a chance to export xwindows nor web interface, with cli you allways know is going to work.
5. As features I think what would be great is a really good implementation with VSE and HPsim.
6.Integrated. with a and b.

7. what I have more problems with is the integration with efi hdw paths and the vpdb, more than once you get that your vpdb is not uptodate, and have to spend some time to get the server to boot

[Mark McDonald_2]

I've worked in several places with vpars in the last few years. None of them have had any need for much manipulation of the setup. I personally do not see any need for a GUI.

Once these Superdomes are in place (usually for billing) thy do not need to be touched. Running vparstatus is so much quicker than launching a gui.....

I've also come across some rp/rx 7/8000 boxes in development environments. These get reconfigured more regularly, but I do not see what benefit a GUI would add?

[Pulse001]

Hi Hemanth,

1) Yes, 7 superdomes with 53 vpars.
2) No, CLI is more than enough.
3) N/A
4) I prefer CLI because i can see and learn all the underlying commands.
5) N/A
6) standalone.
7) Dynamic memory movement across vpars.

[RUET]

1) Yes, 1 RP8440 with 4 npars and 8Vpars and 1 RX with 2 npars and 4 vpars
2) Yes, but CLI is always better (no intermediate layer).
3) N/A
4) both. GUI for admin purposes, CLI for troubleshouting
5) all (as npar manager GUI)
6) both, should be good to have an simple http access for management
7) Dynamic allocations across vpars.

[Basheer_2]

1) Yes, About 20 vPars in 2 Integrity Superdomes.

2) Want

3) 11.23 and 11.31. We have 11.23 and 11.31

4) Both, GUI for Training. Look Matters.

5) good to have same as the CLI. Nice to have CPU/Memory additions, deletions, modifications and document the vPars config (like print_manifest) and can we replicate vPar config if we removed a vPar.
6) Standalone and integrated SMH
7) Too many Tasks/Servers/nPars/vPars.

[Jozef_Novak]

1.) Yes, in the past, during my time with HP.
2 complexes with 6 vpars (3 each)

2.) Definitely not a must. CLI is sufficient.

3.) N/A

4.) CLI - easy to use and ones requires only ssh session to use it.

5.) N/A

6.) If so, then it should be included with VSE.

7.) The necessity to bring down the entire npar when servicing only one vpar. Customers were quite irritated by this.

J.

[F Verschuren]

1 Yes ~20 (after the blades les and les...)

2. I never use a gui so for me no.

3. If you use a GUI normaly you do not know what is behind it, du to our team only manager hpux (and no appilcations) we no not seek a easy way that can manager 90% of the problems, If there is a problem where the gui does not work you need also the genaral info.

4. see above, I do not prefer a gui, however if you only do configurations and no operations, it can be te easey way out.

5. needed:switch mem, switch cpu, enable/ disable cpu
nice to have: ad vpar/remove vpar form the configuration.

6. Intergrated in the vpar software, so that ever vpar configuration has the tool to manage the vpars..

7. none

Kind regards,
FReek