Hello.
Am I the only one getting annoyed by projects like ovirt that seem be just paving over libvirt with way too much API based on python and esp. java? Perhaps I don't understand that project; their wiki is not very forthcoming.
I'd like to announce my interest php-virt-control. I'm reviewing the source & various info and plan to help out, esp. with packaging and portability. I much prefer more focused tools that do their job well than the gigantic-amalgamated-stackware solution.
It would be nice if there were a place to file bugs, if only to have a to-do list.
Is there any reason I should not consider this an active project?
Cheers, _S.
Hi Sean, really thanks for your interest in the project!
The project is not officially support but I didn't say it's not active. The thing is that the project is being developed by just me in my spare time and it's highly dependent on libvirt-php project that I do along with some collegues. I'm a Red Hat engineer and I've had an idea of having php-virt-control project and one of my collegues hosts this on his server however there's no real development currently being done as this is not even in Fedora (although I already have a review request there for about a year or so).
I'm currently pretty busy with work stuff so I'd really appreciate some help on this but unfortunately I don't have a bugzilla for this. I'll try to use our publicly available OpenShift cloud project to install it and let you know the URL then. It may be a really useful thing.
If you have any ideas would be good to implement then please tell me using this list and we'll figure out what would be good to work on. Of course, this is open-source so if you'd like to work on this then I hope you have open-source spirit too ;-)
You can put me to the CC list of the e-mail next time and I'd really appreciate any help with this ;-)
Thanks, Michal
On 03/04/2012 08:13 PM, Sean wrote:
Hello.
Am I the only one getting annoyed by projects like ovirt that seem be just paving over libvirt with way too much API based on python and esp. java? Perhaps I don't understand that project; their wiki is not very forthcoming.
I'd like to announce my interest php-virt-control. I'm reviewing the source & various info and plan to help out, esp. with packaging and portability. I much prefer more focused tools that do their job well than the gigantic-amalgamated-stackware solution.
It would be nice if there were a place to file bugs, if only to have a to-do list.
Is there any reason I should not consider this an active project?
Cheers, _S. _______________________________________________ php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
On 03/04/2012 08:13 PM, Sean wrote:
Hello.
Am I the only one getting annoyed by projects like ovirt that seem be just paving over libvirt with way too much API based on python and esp. java? Perhaps I don't understand that project; their wiki is not very forthcoming.
I'd like to announce my interest php-virt-control. I'm reviewing the source & various info and plan to help out, esp. with packaging and portability. I much prefer more focused tools that do their job well than the gigantic-amalgamated-stackware solution.
It would be nice if there were a place to file bugs, if only to have a to-do list.
Is there any reason I should not consider this an active project?
Cheers, _S. _______________________________________________ php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project & site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotny minovotn@redhat.com To: Virtual machine control for PHP php-virt-control@lists.fedorahosted.org CC: Sean sean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
Well, the bugzilla on the link ( http://bugzilla.php-virt-control.org )I provided should send you the link ASAP. I've seen the database however I didn't see you registration here. Please register to this bugzilla first.
About the package naming I've never thought about it however the project is already having a name and a domain is registered. If applicable we should think of better naming for not just this project but all virtualization-related projects that are not officially supported, like virt-backup and maybe others that could be useful (if we find any).
Or do you mean renaming the debian package to pvc as php-virt-control ? Theoretically we could think about the name of virtual-machine-controller (VMC) since the php-virt-control was badly chosen. There's no need to specify the platform it uses in here (PHP in this case). It could be Virtual Machine Controller, or Web-virt-control, instead. Any name suggestions?
For bugzilla on php-virt-control there are 2 namespaces as this is intended to be a personal bugzilla as well so please look to the "Virtualization related" namespace/classification.
Michal
On 03/12/2012 11:01 PM, Sean wrote:
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project & site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotny minovotn@redhat.com To: Virtual machine control for PHP php-virt-control@lists.fedorahosted.org CC: Sean sean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
The name is not a very big issue to me, but I would suggest considering a change. The domain name "php-virt-control" and product / documentation don't really have to change, but I would suggest the final product release might go by a shorter moniker such as "PVC" so as to be more memorable and easier. This would only affect the RPM, debian, and / or tar-ball releases (pvc.rpm, pvc.tar, etc). Beyond that you could maybe change the base URL of the entry point and if you really wanted to, also the UI.
Using "PVC" has a few advantages; Other than being short and quick, it does not require the project name to change (because it is simply an abbreviation), it may remind the user of "Poly Vinyl Chloride" (a material used in quick-assembly plumbing and high fashion, among others), and it doesn't partly rhyme with "birth control" (an unfortunate coincidence). Even the source repository does not need to be renamed.
Again, I don't think it's a huge issue. The bigger the change the more things it affects. I think "VMC" is too close to "VNC". "web-virt-control" is a pretty simple difference. "webvirt" sounds kind of cool as one word. Anything with more than one hyphen seems troublesome, and anything with "virt-control" has that rhyming problem. "virtigo"? "php-machine"?
I just hit bugzilla.php-virt-control.org 3 times. "Request for new user account 'sean.channel@pacbell.net' submitted" --No love. Network / firewall problem? Default configuration? _S
On 03/13/2012 05:43 AM, Michal Novotny wrote:
Well, the bugzilla on the link ( http://bugzilla.php-virt-control.org )I provided should send you the link ASAP. I've seen the database however I didn't see you registration here. Please register to this bugzilla first.
About the package naming I've never thought about it however the project is already having a name and a domain is registered. If applicable we should think of better naming for not just this project but all virtualization-related projects that are not officially supported, like virt-backup and maybe others that could be useful (if we find any).
Or do you mean renaming the debian package to pvc as php-virt-control ? Theoretically we could think about the name of virtual-machine-controller (VMC) since the php-virt-control was badly chosen. There's no need to specify the platform it uses in here (PHP in this case). It could be Virtual Machine Controller, or Web-virt-control, instead. Any name suggestions?
For bugzilla on php-virt-control there are 2 namespaces as this is intended to be a personal bugzilla as well so please look to the "Virtualization related" namespace/classification.
Michal
On 03/12/2012 11:01 PM, Sean wrote:
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project& site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotnyminovotn@redhat.com To: Virtual machine control for PHPphp-virt-control@lists.fedorahosted.org CC: Seansean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
"php-vm" is kind of snappy also.
_S
On 03/13/2012 12:33 PM, Sean wrote:
The name is not a very big issue to me, but I would suggest considering a change. The domain name "php-virt-control" and product / documentation don't really have to change, but I would suggest the final product release might go by a shorter moniker such as "PVC" so as to be more memorable and easier. This would only affect the RPM, debian, and / or tar-ball releases (pvc.rpm, pvc.tar, etc). Beyond that you could maybe change the base URL of the entry point and if you really wanted to, also the UI.
Using "PVC" has a few advantages; Other than being short and quick, it does not require the project name to change (because it is simply an abbreviation), it may remind the user of "Poly Vinyl Chloride" (a material used in quick-assembly plumbing and high fashion, among others), and it doesn't partly rhyme with "birth control" (an unfortunate coincidence). Even the source repository does not need to be renamed.
Again, I don't think it's a huge issue. The bigger the change the more things it affects. I think "VMC" is too close to "VNC". "web-virt-control" is a pretty simple difference. "webvirt" sounds kind of cool as one word. Anything with more than one hyphen seems troublesome, and anything with "virt-control" has that rhyming problem. "virtigo"? "php-machine"?
I just hit bugzilla.php-virt-control.org 3 times. "Request for new user account 'sean.channel@pacbell.net' submitted" --No love. Network / firewall problem? Default configuration? _S
On 03/13/2012 05:43 AM, Michal Novotny wrote:
Well, the bugzilla on the link ( http://bugzilla.php-virt-control.org )I provided should send you the link ASAP. I've seen the database however I didn't see you registration here. Please register to this bugzilla first.
About the package naming I've never thought about it however the project is already having a name and a domain is registered. If applicable we should think of better naming for not just this project but all virtualization-related projects that are not officially supported, like virt-backup and maybe others that could be useful (if we find any).
Or do you mean renaming the debian package to pvc as php-virt-control ? Theoretically we could think about the name of virtual-machine-controller (VMC) since the php-virt-control was badly chosen. There's no need to specify the platform it uses in here (PHP in this case). It could be Virtual Machine Controller, or Web-virt-control, instead. Any name suggestions?
For bugzilla on php-virt-control there are 2 namespaces as this is intended to be a personal bugzilla as well so please look to the "Virtualization related" namespace/classification.
Michal
On 03/12/2012 11:01 PM, Sean wrote:
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project& site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotnyminovotn@redhat.com To: Virtual machine control for PHPphp-virt-control@lists.fedorahosted.org CC: Seansean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control
Well, I wrote to openshift support about this since the registration e-mail is not going anywhere so the mail server seems to be offline or stuck. We have to wait since they don't provide the root access to the box so I don't have it to investigate myself.
The naming change is not a bad thing provided the fact the docs and domain name won't change as the domain has been registered for 5 years on my own expenses.
Considering the PVC name it's not that good since user may think that this is something chemistry-related (because of mentioned Poly-Vinyl Chloride materials). The change is not that huge, that's correct but it really may be good to change the naming.
So considering the naming I'm appending my comments per each mentioned: php-virt-control - current name PVC - may remind users of chemistry-related stuff because of poly-vinyl chloride VMC - pretty similar name to VNC, may be confusing as well web-virt-control - well, originally my intention was to rename to this one if so however I think we need to figure out something better virt-control - dtto virtigo - honestly, this name is not that bad but we may keep thinking webvirt - this sounds good however still not the best naming yet
It may be great to have some name like for the mystical character or ancient legend character that somehow involves the virtual environment to imply this is about virtual machines. We may need to brainstorm about this... or maybe something like Matrix (the movie), which is basically the virtual environment too. But for this we may face the issues not to confuse this with the matrix (as in mathematical space). We also can't reuse the names from The Matrix (like Zion as city they live in) to call it, let's say, Zion-Controller or similar because of the copyright issues IMHO.
Any ideas about this? The mythical character that's connected somehow would be really great but I can't recall any good character to remind user of the virtual, non-real, environment.
Michal
On 03/13/2012 08:41 PM, Sean wrote:
"php-vm" is kind of snappy also.
_S
On 03/13/2012 12:33 PM, Sean wrote:
The name is not a very big issue to me, but I would suggest considering a change. The domain name "php-virt-control" and product / documentation don't really have to change, but I would suggest the final product release might go by a shorter moniker such as "PVC" so as to be more memorable and easier. This would only affect the RPM, debian, and / or tar-ball releases (pvc.rpm, pvc.tar, etc). Beyond that you could maybe change the base URL of the entry point and if you really wanted to, also the UI.
Using "PVC" has a few advantages; Other than being short and quick, it does not require the project name to change (because it is simply an abbreviation), it may remind the user of "Poly Vinyl Chloride" (a material used in quick-assembly plumbing and high fashion, among others), and it doesn't partly rhyme with "birth control" (an unfortunate coincidence). Even the source repository does not need to be renamed.
Again, I don't think it's a huge issue. The bigger the change the more things it affects. I think "VMC" is too close to "VNC". "web-virt-control" is a pretty simple difference. "webvirt" sounds kind of cool as one word. Anything with more than one hyphen seems troublesome, and anything with "virt-control" has that rhyming problem. "virtigo"? "php-machine"?
I just hit bugzilla.php-virt-control.org 3 times. "Request for new user account 'sean.channel@pacbell.net' submitted" --No love. Network / firewall problem? Default configuration? _S
On 03/13/2012 05:43 AM, Michal Novotny wrote:
Well, the bugzilla on the link ( http://bugzilla.php-virt-control.org )I provided should send you the link ASAP. I've seen the database however I didn't see you registration here. Please register to this bugzilla first.
About the package naming I've never thought about it however the project is already having a name and a domain is registered. If applicable we should think of better naming for not just this project but all virtualization-related projects that are not officially supported, like virt-backup and maybe others that could be useful (if we find any).
Or do you mean renaming the debian package to pvc as php-virt-control ? Theoretically we could think about the name of virtual-machine-controller (VMC) since the php-virt-control was badly chosen. There's no need to specify the platform it uses in here (PHP in this case). It could be Virtual Machine Controller, or Web-virt-control, instead. Any name suggestions?
For bugzilla on php-virt-control there are 2 namespaces as this is intended to be a personal bugzilla as well so please look to the "Virtualization related" namespace/classification.
Michal
On 03/12/2012 11:01 PM, Sean wrote:
I haven't received confirmation emails from either bugzilla or openshift yet (registered for both), so I'll toss this one out there:
I noticed a comment about the name on the package review and I did find it confusing at first, plus every time I read it I hear "birth control".
Rather than change the whole project& site name, would it be worth considering going with simply "pvc" for the package distribution?
_S
-------- Original Message -------- Subject: Re: [php-virt-control] vs. "ovirt" Date: Mon, 12 Mar 2012 19:39:23 +0100 From: Michal Novotnyminovotn@redhat.com To: Virtual machine control for PHPphp-virt-control@lists.fedorahosted.org CC: Seansean.channel@pacbell.net
Hi Sean, I've managed to install bugzilla to OpenShift. It's accessible here:
http://bugzilla.php-virt-control.org/
Please feel free to register, file bugs and write/post patches :-)
Any help is highly appreciated!
Thanks, Michal
php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control
php-virt-control mailing list php-virt-control@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/php-virt-control
php-virt-control@lists.fedorahosted.org
-
Michal Novotny -
Sean