On 07/02/2016 02:19 PM, Achim Patzner wrote: > Hi! > > > Am I the only one who would like an integrated name service management > for local services that will be provisioned at the time of VM creation > (e. g. if you create a machine "builder" its assigned IP address could > be added to the locally running dnsmasq on the NetVM)? This somehow is against the principle of "isolation" between the AppVM... But I can understand that, from a developer point of view, this may be helpful - if, for example, you develop web-apps and assign a web-app per AppVM to host.
Yet, Qubes OS is designed for workstations, and it may be argued that developer workstations may host the services they are developing. I think, IMHO, that this is wrong, and may lead to unnecessary complexity in dealing with the subtleties of the application working on the developer's workstation but not in production. I would recommend to test them on the work AppVM, and then complete testing in a staging environment. I myself built a low-cost staging machine, with proxmox and several VMs with a centos template: my production machines are typical VPSs with centos, so the differences between staging and production are minimal. Beyond the developer point of view, do you think there would be other examples that would benefit from having Qubes AppVMs mutually visible? (thus needing an auto-registering name resolution system?) -- Alex -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/95d64395-fa05-d466-dfa1-0e1e3ddb9c04%40gmx.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
