1 2 3 4 Previous Next 51 Replies Latest reply on Apr 1, 2013 6:35 AM by gkho978 Go to original post
      • 15. Re: VMware Studio v2.2(?): Feature requests / User wish list
        Jogarem Enthusiast

        When defining a proxy server with the VMware web interface or with the "Network Settings" dialog inside the text console only the "http_proxy" variable is set in /etc/environment.

         

        A great enhancement would be:

         

        • enable https proxy (add https_proxy variable)

        • enable ftp proxy (add ftp_proxy variable)

        • enable exclusions (add no_proxy variable)

         

        Another needed feature is the setting of username / password in console setup:

         

        • With the command line tool for network and proxy configueration it is not possible to set an proxy username and passwd

         

        this is added as FR #022 in the first post of this thread.

         

        Regards

        Thomas

        • 16. Re: VMware Studio v2.2(?): Feature requests / User wish list
          angusmojo2008 Lurker

           

          My main request will be to have a real support of vCloud Director from VMware Studio's generated appliance.

           

           

          I'm refering to this issue w/ VAMI:

           

           

          VAMI compatibility

           

           

          One could expect that any Studio's OVF will be plainly compliant w/ vCloud Director.

           

           

          It's a real mess OVF properties that VMware Studio uses are not understable by vCloud Director.

           

           

          As for the load-balancing and vpn features of the edge device not useable from vCloud Director UI or API, it seems that vCloud director was released w/o any cross-products synchronisation!

           

           

          • 17. Re: VMware Studio v2.2(?): Feature requests / User wish list
            Jogarem Enthusiast

            Hello angusmojo and many thanks for your feedback!

             

            Unfortunately I have no experience with vCloud Director but what I had understood from your request was that the OVF file generated with Studio is not compatible with vCloud Director?

             

            But on the other hand you mentioned problems with OVF properties and the link you have written points to problems with the connection so I'm not sure if you really mean that not the OVF file itself is a problem but the installed build (created with Studio) can not be detected by vCloud Director?! Is that correct or can you specify it a little more?

             

            What impact does this issue have for you where P1 = highest priority ....P4 = lowest priority

             

            Regards

            Thomas

            • 18. Re: VMware Studio v2.2(?): Feature requests / User wish list
              youc Novice
              • are there any plans to add support for Windows server 2008 R2?

               

              • currently, vmware studio doesn't support building a vm using customized windows ISO image. if next version can support such builds, that will be really helpful

               

              • I wonder why vm's (windows vms) built in esx server cannot be seen and used by studio to build a vApp. it will greatly simplify the task of creating vApps using studio.

              • 19. Re: VMware Studio v2.2(?): Feature requests / User wish list
                Jogarem Enthusiast

                Hello youc!

                 

                Thanks for your request - I have added the requests to the list with priority classes because you haven't mention your priority I have defined them as I think so (but you can tell me other if you want to):

                 

                • Support for Windows server 2008 R2
                  • P2
                • Enable the use of customized windows ISO image
                  • P2
                • VM's created by ESX server cannot be seen and used by studio to build a vApp
                  • P3

                 

                If you need or want other priority classes - no problem, please tell me which priority you expect for each issue.

                 

                Regards

                Thomas

                • 20. Re: VMware Studio v2.2(?): Feature requests / User wish list
                  Jogarem Enthusiast

                  A new bug was reported (Studio 2.1, Ubuntu Linux 8.04 VM):

                   

                  When using proxy authentication and define the username + password in the VMware Web GUI you cannot use special characters.

                  Special characters (tested with username containing a minus sign "-" ) are converted to some unreadable characters ("-" will be "%2D").

                   

                  I have tested that for the password, too and it is the same problem here. All special characters are converted so the GUI is completely unusable with standard secure passwords and usernames..

                   

                  Regards

                  Thomas

                   

                  PS: Added it to the FR list - P2

                  • 21. Re: VMware Studio v2.2(?): Feature requests / User wish list
                    youc Novice

                    Hi Thomas,

                    thanks for adding them in the feature list. here are my views on putting priorities to these requests

                     

                    Support for Windows server 2008 R2

                    Windows server 2008 R2 is mainstream windows OS and SP1will be coming in a month or two. I think it should really be added as a supported guest OS (both R2 and R2 SP1) and hence, should be considered as P1.

                     

                    Enable the use of customized windows ISO image

                    I am ok with its current priority. what I am looking for is, it should support building a vm using customized ISO that initially boots into custom Windows PE and OS installation is launched from there.

                     

                    • VM's created by ESX server cannot be seen and used by studio to build a vApp
                      • P3 - that's ok

                     

                    I am sorry for my lack of knowledge about vmware studio and vApps..however, I am curious to know the difference between vApps created using vSphere client and vmware studio. are they any significant differences (ie. something special that vmware studio can do but vSphere client can't). Its easy to create vm and vApp using vSphere client and it does take care of my first two requests as well.

                     

                    Thanks

                    • 22. Re: VMware Studio v2.2(?): Feature requests / User wish list
                      Jogarem Enthusiast

                      umesh wrote:

                       

                      Hi Thomas,

                      thanks for adding them in the feature list.

                       

                      You're welcome! I'm always happy for every feedback so the FR list can be expanded

                       

                      umesh wrote:

                       

                      Support for Windows server 2008 R2

                      should be considered as P1.

                       

                      Done!

                       

                      umesh wrote:

                       

                      I am sorry for my lack of knowledge about vmware studio and vApps..however, I am curious to know the difference between vApps created using vSphere client and vmware studio. are they any significant differences (ie. something special that vmware studio can do but vSphere client can't). Its easy to create vm and vApp using vSphere client and it does take care of my first two requests as well.

                       

                      Thanks

                       

                      Hm take a look at the Studio documentation for deeper look at vApps with Studio. I'm (generally) not using vApps by myself but the possible difference is the complete and easy handling of different builds in your Studio vApp (easily choosing different builds of different VMs). But I think it depends on your use case and as I said before I don't use vApps at the moment so maybe there are really good reasons to use vSphere or Studio for vApps but I don't know them..

                      I use Studio to build different Linux systems including the management of all the update issues. If you have  the need to simply create a server only and do not care about updating etc and if you want to handle all the installation by yourself and not automated - I believe then you don't need Studio for this.

                       

                      In my opinion Studio is a very good tool for:

                      1. automatic and non interactive installation of VMs
                      2. create your own software packages (e.g. your selfmade application or some 3rd party application which you need to maintain)
                      3. keep your software packages up to date

                       

                      But that's maybe only my opinion so if you want a better answer you should ask the question regarding vSphere/Studio + vApps in a new thread. This thread here is only read by people which want to have new features so maybe you have more luck when openening a new one.

                       

                      Regards

                      Thomas

                      • 23. Re: VMware Studio v2.2(?): Feature requests / User wish list
                        youc Novice

                        thanks Thomas.

                        I will put it my query about vApps/studio/vsphere in new thread.

                         

                        Regards,

                        umesh

                        • 24. Re: VMware Studio v2.2(?): Feature requests / User wish list
                          Jogarem Enthusiast

                          new FR arrived:

                           

                          affects: VMware Studio Build GUI

                           

                           

                          It should be possible to "lock" or "freeze"

                          • a specific profile
                          • a specific build in profile

                           

                           

                          Reason:

                          When you want to prevent the deleting or editing of a specific release you should have the possibility to lock/freeze it.

                          A lock/freeze of a whole profile (means no build possible anymore! until unlocked) will prevent builds which are not

                          wanted anymore at all even when I want to keep the profile.

                           

                           

                          It should be possible to give a specific build a name

                          • when you have finished a build you should have the possibility to name this so you can see easily in the GUI those builds
                          • examples: "Final release with 10GB" or "Starting point for my other profile"

                           

                          Reason:

                          With this feature it would be no problem anymore to find out the important builds and it prevents deleting specific builds

                          because I can see immediately what the purpose of this build is.

                           

                           

                          Those would be very handy features!

                           

                          Regards

                          Thomas

                           

                          PS: added as FR#027

                          • 25. Re: VMware Studio v2.2(?): Feature requests / User wish list
                            provision Hot Shot
                            VMware Employees

                            You may enable W2K8 R2 support in Studio 2.1 with the steps mentioned in http://communities.vmware.com/message/1698836#1698836. Hope that helps.

                            • 26. Re: VMware Studio v2.2(?): Feature requests / User wish list
                              provision Hot Shot
                              VMware Employees

                              > I wonder why vm's (windows vms) built in esx server cannot be seen and used by studio to build a vApp. it will greatly simplify the task of creating vApps using studio.

                               

                              In regards to the above, in order for Studio to take an existing VM as an input and build on top of it, there needs to be a Studio agent running in the input VM to work with Studio. Currently there isn't such agent (nor any Studio runtime component a.k.a VAMI) for Windows OS.

                              • 27. Re: VMware Studio v2.2(?): Feature requests / User wish list
                                Jogarem Enthusiast

                                added new FR#028 which points to a design feature for Studio GUI

                                • 28. Re: VMware Studio v2.2(?): Feature requests / User wish list
                                  Jogarem Enthusiast

                                  @VMware:

                                   

                                  Do you have a release date for a new version of Studio?

                                  The high priority issues described in this thread getting more and more problematic..

                                   

                                  Kind regards

                                  Thomas

                                  • 29. Re: VMware Studio v2.2(?): Feature requests / User wish list
                                    cskowmh Enthusiast

                                    I too am worried about this. We're trying to hack things together, and judging from earlier messages we may have issues deploying anything with OVF properties in vCloud director.