I am planning to schedule a monthly XCP meeting for the community and am struggling with when to host the call. As we are a global community, there is no single optimal time to host the meeting. In an effort to support the most likely attendees, please send me your time zone if you plan to participate in these calls. I will track the most common time zones in an effort to maximize attendance. All meetings will have notes taken which will be posted on the Xen.org wiki for those of you unable to participate. Stephen Spector Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org http://blog.xen.org | @xen_com_mgr _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
On Wed, May 05, 2010 at 01:28:55PM -0400, Stephen Spector wrote:> I am planning to schedule a monthly XCP meeting for the community and am > struggling with when to host the call. As we are a global community, there > is no single optimal time to host the meeting. In an effort to support the > most likely attendees, please send me your time zone if you plan to > participate in these calls. I will track the most common time zones in an > effort to maximize attendance. All meetings will have notes taken which > will be posted on the Xen.org wiki for those of you unable to participate. >Great idea! I was actually thinking about this at the Summit last week, but forgot to talk about it.. Good that you thought about it :) -- Pasi _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
Europe/Rome. Thanks and regards, FG Da: xen-api-bounces@lists.xensource.com [mailto:xen-api-bounces@lists.xensource.com] Per conto di Stephen Spector Inviato: mercoledì 5 maggio 2010 19:29 A: xen-devel@lists.xensource.com; xen-api@lists.xensource.com Oggetto: [Xen-API] XCP Monthly Call Request I am planning to schedule a monthly XCP meeting for the community and am struggling with when to host the call. As we are a global community, there is no single optimal time to host the meeting. In an effort to support the most likely attendees, please send me your time zone if you plan to participate in these calls. I will track the most common time zones in an effort to maximize attendance. All meetings will have notes taken which will be posted on the Xen.org wiki for those of you unable to participate. Stephen Spector Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org http://blog.xen.org | @xen_com_mgr _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
Dear Stephen, My current timezone is America/Sao_Paulo, which at this time of the year overlaps with UTC-3. Thanks for the awesome initiative! Regards Evaldo ***Sent via RoadSync® for Android™ From: Stephen Spector Sent: May 05, 2010 2:29 PM To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com Subject: [Xen-API] XCP Monthly Call Request I am planning to schedule a monthly XCP meeting for the community and am struggling with when to host the call. As we are a global community, there is no single optimal time to host the meeting. In an effort to support the most likely attendees, please send me your time zone if you plan to participate in these calls. I will track the most common time zones in an effort to maximize attendance. All meetings will have notes taken which will be posted on the Xen.org wiki for those of you unable to participate. Stephen Spector Xen.org Community Manager T: (772) 621-5062 | M: (954) 854-4257 stephen.spector@xen.org http://blog.xen.org | @xen_com_mgr ________________________________ AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/. NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information. If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/. _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
I''ve been trying to emulate the Xen antispoof features in XCP. This requires the xt_physdev iptables extension. Here''s what I''ve done: 1. Downloaded the XCP DDK VM and installed it 2. Downloaded the Dom0 kernel sources from http://www.xen.org/files/XenCloud/Software/latest/sources/source-1.iso to a running DDK VM instance 3. make menuconfig inside the kernel sources and enable physdev inside Networking->Network Packet Filtering->Core Netfilter Configuration->physdev match support 4. make modules modules_install inside the kernel sources 5. Copy resulting xt_physdev.ko to dom0 6. insmod results in an error: insmod ./xt_physdev.ko insmod: error inserting ''./xt_physdev.ko'': -1 Unknown symbol in module dmesg shows the error to be: xt_physdev: disagrees about version of symbol xt_register_matches xt_physdev: Unknown symbol xt_register_matches Modinfo reports the correct version: # modinfo xt_physdev.ko filename: xt_physdev.ko alias: ip6t_physdev alias: ipt_physdev description: Xtables: Bridge physical device match author: Bart De Schuymer <bdschuym@pandora.be> license: GPL srcversion: 4D030E98D0F909D8DA92F33 depends: x_tables supported: yes vermagic: 2.6.27.42-0.1.1.xs0.1.1.737.1065xen SMP mod_unload modversions Xen 686 It seems that it requires a complete kernel rebuild and re-install. Can anybody confirm this or help me with an alternate way of building required iptables extensions? Thanks -- C V _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
C V wrote:> I''ve been trying to emulate the Xen antispoof features in XCP. This requires the xt_physdev iptables extension. Here''s what I''ve done: > 1. Downloaded the XCP DDK VM and installed it > 2. Downloaded the Dom0 kernel sources from http://www.xen.org/files/XenCloud/Software/latest/sources/source-1.iso to a running DDK VM instance > 3. make menuconfig inside the kernel sources and enable physdev inside Networking->Network Packet Filtering->Core Netfilter Configuration->physdev match support > 4. make modules modules_install inside the kernel sources > 5. Copy resulting xt_physdev.ko to dom0 >I think step 4 will copy the modulo in /lib/modules/kern-version/..> 6. insmod results in an error: > insmod ./xt_physdev.ko > insmod: error inserting ''./xt_physdev.ko'': -1 Unknown symbol in module >Did you depmod after installing the modules?> dmesg shows the error to be: > xt_physdev: disagrees about version of symbol xt_register_matches > xt_physdev: Unknown symbol xt_register_matches > Modinfo reports the correct version: > # modinfo xt_physdev.ko > filename: xt_physdev.ko > alias: ip6t_physdev > alias: ipt_physdev > description: Xtables: Bridge physical device match > author: Bart De Schuymer <bdschuym@pandora.be> > license: GPL > srcversion: 4D030E98D0F909D8DA92F33 > depends: x_tables > supported: yes > vermagic: 2.6.27.42-0.1.1.xs0.1.1.737.1065xen SMP mod_unload modversions Xen 686 > > > It seems that it requires a complete kernel rebuild and re-install. Can anybody confirm this or help me with an alternate way of building required iptables extensions? > > Thanks > -- > C V > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Jorge Armando Medina Computación Gráfica de México Web: http://www.e-compugraf.com Tel: 55 51 40 72, Ext: 124 Email: jmedina@e-compugraf.com GPG Key: 1024D/28E40632 2007-07-26 GPG Fingerprint: 59E2 0C7C F128 B550 B3A6 D3AF C574 8422 28E4 0632 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks I got the xt_physdev.ko from /lib/modules/ inside the DDK VM and copied it to dom0 /lib/modules/... I ran depmod inside dom0 and modprobe xt_physdev in dom0 results in the same problem. ----- Original Message ---- From: Jorge Armando Medina <jmedina@e-compugraf.com> To: xen-users@lists.xensource.com Sent: Mon, May 10, 2010 12:03:46 PM Subject: Re: [Xen-users] XCP antispoof C V wrote:> I''ve been trying to emulate the Xen antispoof features in XCP. This requires the xt_physdev iptables extension. Here''s what I''ve done: > 1. Downloaded the XCP DDK VM and installed it > 2. Downloaded the Dom0 kernel sources from http://www.xen.org/files/XenCloud/Software/latest/sources/source-1.iso to a running DDK VM instance > 3. make menuconfig inside the kernel sources and enable physdev inside Networking->Network Packet Filtering->Core Netfilter Configuration->physdev match support > 4. make modules modules_install inside the kernel sources > 5. Copy resulting xt_physdev.ko to dom0 >I think step 4 will copy the modulo in /lib/modules/kern-version/..> 6. insmod results in an error: > insmod ./xt_physdev.ko > insmod: error inserting ''./xt_physdev.ko'': -1 Unknown symbol in module >Did you depmod after installing the modules?> dmesg shows the error to be: > xt_physdev: disagrees about version of symbol xt_register_matches > xt_physdev: Unknown symbol xt_register_matches > Modinfo reports the correct version: > # modinfo xt_physdev.ko > filename: xt_physdev.ko > alias: ip6t_physdev > alias: ipt_physdev > description: Xtables: Bridge physical device match > author: Bart De Schuymer <bdschuym@pandora.be> > license: GPL > srcversion: 4D030E98D0F909D8DA92F33 > depends: x_tables > supported: yes > vermagic: 2.6.27.42-0.1.1.xs0.1.1.737.1065xen SMP mod_unload modversions Xen 686 > > > It seems that it requires a complete kernel rebuild and re-install. Can anybody confirm this or help me with an alternate way of building required iptables extensions? > > Thanks > -- > C V > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Jorge Armando Medina Computación Gráfica de México Web: http://www.e-compugraf.com Tel: 55 51 40 72, Ext: 124 Email: jmedina@e-compugraf.com GPG Key: 1024D/28E40632 2007-07-26 GPG Fingerprint: 59E2 0C7C F128 B550 B3A6 D3AF C574 8422 28E4 0632 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Stephen, I''m at same timezone as Evaldo, UTC-3. Regards, Lucas de Souza Santos (ldss) On Fri, May 7, 2010 at 6:46 AM, Evaldo Gardenali <egardenali@uolinc.com>wrote:> Dear Stephen, > > My current timezone is America/Sao_Paulo, which at this time of the year > overlaps with UTC-3. > > Thanks for the awesome initiative! > > Regards > > Evaldo > > ***Sent via RoadSync® for Android™ > > From: Stephen Spector > Sent: May 05, 2010 2:29 PM > To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com > Subject: [Xen-API] XCP Monthly Call Request > > > I am planning to schedule a monthly XCP meeting for the community and am > struggling with when to host the call. As we are a global community, there > is no single optimal time to host the meeting. In an effort to support the > most likely attendees, please send me your time zone if you plan to > participate in these calls. I will track the most common time zones in an > effort to maximize attendance. All meetings will have notes taken which will > be posted on the Xen.org wiki for those of you unable to participate. > > > > *Stephen Spector* > > > > Xen.org Community Manager > > *T:* (772) 621-5062 | *M:* (954) 854-4257 > > stephen.spector@xen.org > > http://blog.xen.org | @xen_com_mgr > > > > ------------------------------ > AVISO: A informação contida neste e-mail, bem como em qualquer de seus > anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) > acima referido(s), podendo conter informações sigilosas e/ou legalmente > protegidas. Caso você não seja o destinatário desta mensagem, informamos que > qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de > seus anexos é absolutamente proibida. Solicitamos que o remetente seja > comunicado imediatamente, respondendo esta mensagem, e que o original desta > mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão > realizada a partir destes, sejam permanentemente apagados e/ou destruídos. > Informações adicionais sobre nossa empresa podem ser obtidas no site > http://sobre.uol.com.br/. > > NOTICE: The information contained in this e-mail and any attachments > thereto is CONFIDENTIAL and is intended only for use by the recipient named > herein and may contain legally privileged and/or secret information. > If you are not the e-mail´s intended recipient, you are hereby notified > that any dissemination, distribution or copy of this e-mail, and/or any > attachments thereto, is strictly prohibited. Please immediately notify the > sender replying to the above mentioned e-mail address, and permanently > delete and/or destroy the original and any copy of this e-mail and/or its > attachments, as well as any printout thereof. Additional information about > our company may be obtained through the site http://www.uol.com.br/ir/. > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > >_______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
Before you did this did you test to see if the standard XCP setup with openvswitch is in fact ''spoofable''? You may be able to accomplish the same results by using flows in openvswitch itself rather than going to the trouble of using iptables rules. It might be worth asking the ovs mailing list. Interested to know how you get on, Matt. On Mon, May 10, 2010 8:46 pm, C V wrote:> Thanks > I got the xt_physdev.ko from /lib/modules/ inside the DDK VM and copied it > to dom0 /lib/modules/... > I ran depmod inside dom0 and modprobe xt_physdev in dom0 results in the > same problem. > > ----- Original Message ---- > From: Jorge Armando Medina <jmedina@e-compugraf.com> > To: xen-users@lists.xensource.com > Sent: Mon, May 10, 2010 12:03:46 PM > Subject: Re: [Xen-users] XCP antispoof > > C V wrote: >> I''ve been trying to emulate the Xen antispoof features in XCP. This >> requires the xt_physdev iptables extension. Here''s what I''ve done: >> 1. Downloaded the XCP DDK VM and installed it >> 2. Downloaded the Dom0 kernel sources from >> http://www.xen.org/files/XenCloud/Software/latest/sources/source-1.iso >> to a running DDK VM instance >> 3. make menuconfig inside the kernel sources and enable physdev inside >> Networking->Network Packet Filtering->Core Netfilter >> Configuration->physdev match support >> 4. make modules modules_install inside the kernel sources >> 5. Copy resulting xt_physdev.ko to dom0 >> > I think step 4 will copy the modulo in /lib/modules/kern-version/.. >> 6. insmod results in an error: >> insmod ./xt_physdev.ko >> insmod: error inserting ''./xt_physdev.ko'': -1 Unknown symbol in module >> > Did you depmod after installing the modules? > >> dmesg shows the error to be: >> xt_physdev: disagrees about version of symbol xt_register_matches >> xt_physdev: Unknown symbol xt_register_matches >> Modinfo reports the correct version: >> # modinfo xt_physdev.ko >> filename: xt_physdev.ko >> alias: ip6t_physdev >> alias: ipt_physdev >> description: Xtables: Bridge physical device match >> author: Bart De Schuymer <bdschuym@pandora.be> >> license: GPL >> srcversion: 4D030E98D0F909D8DA92F33 >> depends: x_tables >> supported: yes >> vermagic: 2.6.27.42-0.1.1.xs0.1.1.737.1065xen SMP mod_unload >> modversions Xen 686 >> >> >> It seems that it requires a complete kernel rebuild and re-install. Can >> anybody confirm this or help me with an alternate way of building >> required iptables extensions? >> >> Thanks >> -- >> C V_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I look deeper in openswitch... I found no way to have nice spoofing protection without openflow controller. And yes, spoofing is possible, I check it. Following lines to ovs-ofctl enables mac security (drop any traffic from VM with incorrect combination of MAC address and IP, settings work only for certain MAC/IP): ovs-ofctl add-flow xenbr0 "dl_src=36:75:e2:35:d7:ea priority=39000 dl_type=0x0800 nw_src=18.93.16.25 idle_timeout=65000 action=normal" ovs-ofctl add-flow xenbr0 "dl_src=36:75:e2:35:d7:ea priority=38000 dl_type=0x0800 nw_src=ANY idle_timeout=65000 action=drop" And we can bind mac to interface (port security): ovs-ofctl add-flow xenbr0 "in_port=2 priority=39000 dl_type=0x0800 nw_src=188.93.16.253 idle_timeout=65000 action=normal" ovs-ofctl add-flow xenbr0 "in_port=2 priority=38500 dl_type=0x0806 idle_timeout=65000 action=normal" #пока пускаем ARP без контроля. ovs-ofctl add-flow xenbr0 "in_port=2 priority=38000 idle_timeout=65000 action=drop" The main problems I see here is: 1) Those line washed away after idle_timeout. 2) They are not associated with vm migration process 3) Port number hard to obtain (about 3 greps from xe/ovs output). I still did not tried to install/use openflow controller (may be this will be gold solution?), but direct control of openflow for OVS is very tricky and may cause some unpleasant results in product environment. 11.05.10, 11:39, "Matthew Law" <matt@webcontracts.co.uk>:> Before you did this did you test to see if the standard XCP setup with > openvswitch is in fact ''spoofable''? > > You may be able to accomplish the same results by using flows in > openvswitch itself rather than going to the trouble of using iptables > rules. It might be worth asking the ovs mailing list. > > Interested to know how you get on, > > Matt. > > On Mon, May 10, 2010 8:46 pm, C V wrote: > > Thanks > > I got the xt_physdev.ko from /lib/modules/ inside the DDK VM and copied it > > to dom0 /lib/modules/... > > I ran depmod inside dom0 and modprobe xt_physdev in dom0 results in the > > same problem. > > > > ----- Original Message ---- > > From: Jorge Armando Medina > > To: xen-users@lists.xensource.com > > Sent: Mon, May 10, 2010 12:03:46 PM > > Subject: Re: [Xen-users] XCP antispoof > > > > C V wrote: > >> I''ve been trying to emulate the Xen antispoof features in XCP. This > >> requires the xt_physdev iptables extension. Here''s what I''ve done: > >> 1. Downloaded the XCP DDK VM and installed it > >> 2. Downloaded the Dom0 kernel sources from > >> http://www.xen.org/files/XenCloud/Software/latest/sources/source-1.iso > >> to a running DDK VM instance > >> 3. make menuconfig inside the kernel sources and enable physdev inside > >> Networking->Network Packet Filtering->Core Netfilter > >> Configuration->physdev match support > >> 4. make modules modules_install inside the kernel sources > >> 5. Copy resulting xt_physdev.ko to dom0 > >> > > I think step 4 will copy the modulo in /lib/modules/kern-version/.. > >> 6. insmod results in an error: > >> insmod ./xt_physdev.ko > >> insmod: error inserting ''./xt_physdev.ko'': -1 Unknown symbol in module > >> > > Did you depmod after installing the modules? > > > >> dmesg shows the error to be: > >> xt_physdev: disagrees about version of symbol xt_register_matches > >> xt_physdev: Unknown symbol xt_register_matches > >> Modinfo reports the correct version: > >> # modinfo xt_physdev.ko > >> filename: xt_physdev.ko > >> alias: ip6t_physdev > >> alias: ipt_physdev > >> description: Xtables: Bridge physical device match > >> author: Bart De Schuymer > >> license: GPL > >> srcversion: 4D030E98D0F909D8DA92F33 > >> depends: x_tables > >> supported: yes > >> vermagic: 2.6.27.42-0.1.1.xs0.1.1.737.1065xen SMP mod_unload > >> modversions Xen 686 > >> > >> > >> It seems that it requires a complete kernel rebuild and re-install. Can > >> anybody confirm this or help me with an alternate way of building > >> required iptables extensions? > >> > >> Thanks > >> -- > >> C V > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- wBR,George. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Stephen: Me also like Evaldo and Lucas. My time zone is: UTC-3 Cheers, On Mon, May 10, 2010 at 4:58 PM, Lucas Santos <lucasdss@gmail.com> wrote:> Hi Stephen, > I''m at same timezone as Evaldo, UTC-3. > Regards, > Lucas de Souza Santos (ldss) > > > > On Fri, May 7, 2010 at 6:46 AM, Evaldo Gardenali <egardenali@uolinc.com> > wrote: >> >> Dear Stephen, >> >> My current timezone is America/Sao_Paulo, which at this time of the year >> overlaps with UTC-3. >> >> Thanks for the awesome initiative! >> >> Regards >> >> Evaldo >> >> ***Sent via RoadSync® for Android™ >> >> From: Stephen Spector >> Sent: May 05, 2010 2:29 PM >> To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com >> Subject: [Xen-API] XCP Monthly Call Request >> >> >> I am planning to schedule a monthly XCP meeting for the community and am >> struggling with when to host the call. As we are a global community, there >> is no single optimal time to host the meeting. In an effort to support the >> most likely attendees, please send me your time zone if you plan to >> participate in these calls. I will track the most common time zones in an >> effort to maximize attendance. All meetings will have notes taken which will >> be posted on the Xen.org wiki for those of you unable to participate. >> >> >> >> Stephen Spector >> >> >> >> Xen.org Community Manager >> >> T: (772) 621-5062 | M: (954) 854-4257 >> >> stephen.spector@xen.org >> >> http://blog.xen.org | @xen_com_mgr >> >> >> >> ________________________________ >> AVISO: A informação contida neste e-mail, bem como em qualquer de seus >> anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) >> acima referido(s), podendo conter informações sigilosas e/ou legalmente >> protegidas. Caso você não seja o destinatário desta mensagem, informamos que >> qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de >> seus anexos é absolutamente proibida. Solicitamos que o remetente seja >> comunicado imediatamente, respondendo esta mensagem, e que o original desta >> mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão >> realizada a partir destes, sejam permanentemente apagados e/ou destruídos. >> Informações adicionais sobre nossa empresa podem ser obtidas no site >> http://sobre.uol.com.br/. >> >> NOTICE: The information contained in this e-mail and any attachments >> thereto is CONFIDENTIAL and is intended only for use by the recipient named >> herein and may contain legally privileged and/or secret information. >> If you are not the e-mail´s intended recipient, you are hereby notified >> that any dissemination, distribution or copy of this e-mail, and/or any >> attachments thereto, is strictly prohibited. Please immediately notify the >> sender replying to the above mentioned e-mail address, and permanently >> delete and/or destroy the original and any copy of this e-mail and/or its >> attachments, as well as any printout thereof. Additional information about >> our company may be obtained through the site http://www.uol.com.br/ir/. >> >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xensource.com >> http://lists.xensource.com/mailman/listinfo/xen-api >> > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > >-- Marco Sinhoreli _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api
Pasi Kärkkäinen
2010-May-13 11:39 UTC
Re: [Xen-devel] Re: [Xen-API] XCP Monthly Call Request
On Wed, May 12, 2010 at 07:29:16PM -0300, Marco Sinhoreli wrote:> Hello Stephen: > > Me also like Evaldo and Lucas. > > My time zone is: UTC-3 >And mine is UTC+3 -- Pasi> Cheers, > > On Mon, May 10, 2010 at 4:58 PM, Lucas Santos <lucasdss@gmail.com> wrote: > > Hi Stephen, > > I''m at same timezone as Evaldo, UTC-3. > > Regards, > > Lucas de Souza Santos (ldss) > > > > > > > > On Fri, May 7, 2010 at 6:46 AM, Evaldo Gardenali <egardenali@uolinc.com> > > wrote: > >> > >> Dear Stephen, > >> > >> My current timezone is America/Sao_Paulo, which at this time of the year > >> overlaps with UTC-3. > >> > >> Thanks for the awesome initiative! > >> > >> Regards > >> > >> Evaldo > >> > >> ***Sent via RoadSync® for Android??? > >> > >> From: Stephen Spector > >> Sent: May 05, 2010 2:29 PM > >> To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com > >> Subject: [Xen-API] XCP Monthly Call Request > >> > >> > >> I am planning to schedule a monthly XCP meeting for the community and am > >> struggling with when to host the call. As we are a global community, there > >> is no single optimal time to host the meeting. In an effort to support the > >> most likely attendees, please send me your time zone if you plan to > >> participate in these calls. I will track the most common time zones in an > >> effort to maximize attendance. All meetings will have notes taken which will > >> be posted on the Xen.org wiki for those of you unable to participate. > >> > >> > >> > >> Stephen Spector > >> > >> > >> > >> Xen.org Community Manager > >> > >> T: (772) 621-5062 | M: (954) 854-4257 > >> > >> stephen.spector@xen.org > >> > >> http://blog.xen.org | @xen_com_mgr > >> > >> > >> > >> ________________________________ > >> AVISO: A informação contida neste e-mail, bem como em qualquer de seus > >> anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) > >> acima referido(s), podendo conter informações sigilosas e/ou legalmente > >> protegidas. Caso você não seja o destinatário desta mensagem, informamos que > >> qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de > >> seus anexos é absolutamente proibida. Solicitamos que o remetente seja > >> comunicado imediatamente, respondendo esta mensagem, e que o original desta > >> mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão > >> realizada a partir destes, sejam permanentemente apagados e/ou destruídos. > >> Informações adicionais sobre nossa empresa podem ser obtidas no site > >> http://sobre.uol.com.br/. > >> > >> NOTICE: The information contained in this e-mail and any attachments > >> thereto is CONFIDENTIAL and is intended only for use by the recipient named > >> herein and may contain legally privileged and/or secret information. > >> If you are not the e-mail??s intended recipient, you are hereby notified > >> that any dissemination, distribution or copy of this e-mail, and/or any > >> attachments thereto, is strictly prohibited. Please immediately notify the > >> sender replying to the above mentioned e-mail address, and permanently > >> delete and/or destroy the original and any copy of this e-mail and/or its > >> attachments, as well as any printout thereof. Additional information about > >> our company may be obtained through the site http://www.uol.com.br/ir/. > >> > >> _______________________________________________ > >> xen-api mailing list > >> xen-api@lists.xensource.com > >> http://lists.xensource.com/mailman/listinfo/xen-api > >> > > > > > > _______________________________________________ > > xen-api mailing list > > xen-api@lists.xensource.com > > http://lists.xensource.com/mailman/listinfo/xen-api > > > > > > > > -- > Marco Sinhoreli > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2010/5/13 Pasi Kärkkäinen <pasik@iki.fi>:> On Wed, May 12, 2010 at 07:29:16PM -0300, Marco Sinhoreli wrote: >> Hello Stephen: >> >> Me also like Evaldo and Lucas. >> >> My time zone is: UTC-3 >> > > > And mine is UTC+3 > > -- Pasi > >> Cheers, >> >> On Mon, May 10, 2010 at 4:58 PM, Lucas Santos <lucasdss@gmail.com> wrote: >> > Hi Stephen, >> > I''m at same timezone as Evaldo, UTC-3. >> > Regards, >> > Lucas de Souza Santos (ldss) >> > >> > >> > >> > On Fri, May 7, 2010 at 6:46 AM, Evaldo Gardenali <egardenali@uolinc.com> >> > wrote: >> >> >> >> Dear Stephen, >> >> >> >> My current timezone is America/Sao_Paulo, which at this time of the year >> >> overlaps with UTC-3. >> >> >> >> Thanks for the awesome initiative! >> >> >> >> Regards >> >> >> >> Evaldo >> >> >> >> ***Sent via RoadSync® for Android??? >> >> >> >> From: Stephen Spector >> >> Sent: May 05, 2010 2:29 PM >> >> To: xen-devel@lists.xensource.com, xen-api@lists.xensource.com >> >> Subject: [Xen-API] XCP Monthly Call Request >> >> >> >> >> >> I am planning to schedule a monthly XCP meeting for the community and am >> >> struggling with when to host the call. As we are a global community, there >> >> is no single optimal time to host the meeting. In an effort to support the >> >> most likely attendees, please send me your time zone if you plan to >> >> participate in these calls. I will track the most common time zones in an >> >> effort to maximize attendance. All meetings will have notes taken which will >> >> be posted on the Xen.org wiki for those of you unable to participate. >> >> >> >> >> >> >> >> Stephen Spector >> >> >> >> >> >> >> >> Xen.org Community Manager >> >> >> >> T: (772) 621-5062 | M: (954) 854-4257 >> >> >> >> stephen.spector@xen.org >> >> >> >> http://blog.xen.org | @xen_com_mgr >> >> >> >> >> >> >> >> ________________________________ >> >> AVISO: A informação contida neste e-mail, bem como em qualquer de seus >> >> anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) >> >> acima referido(s), podendo conter informações sigilosas e/ou legalmente >> >> protegidas. Caso você não seja o destinatário desta mensagem, informamos que >> >> qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de >> >> seus anexos é absolutamente proibida. Solicitamos que o remetente seja >> >> comunicado imediatamente, respondendo esta mensagem, e que o original desta >> >> mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão >> >> realizada a partir destes, sejam permanentemente apagados e/ou destruídos. >> >> Informações adicionais sobre nossa empresa podem ser obtidas no site >> >> http://sobre.uol.com.br/. >> >> >> >> NOTICE: The information contained in this e-mail and any attachments >> >> thereto is CONFIDENTIAL and is intended only for use by the recipient named >> >> herein and may contain legally privileged and/or secret information. >> >> If you are not the e-mail??s intended recipient, you are hereby notified >> >> that any dissemination, distribution or copy of this e-mail, and/or any >> >> attachments thereto, is strictly prohibited. Please immediately notify the >> >> sender replying to the above mentioned e-mail address, and permanently >> >> delete and/or destroy the original and any copy of this e-mail and/or its >> >> attachments, as well as any printout thereof. Additional information about >> >> our company may be obtained through the site http://www.uol.com.br/ir/. >> >> >> >> _______________________________________________ >> >> xen-api mailing list >> >> xen-api@lists.xensource.com >> >> http://lists.xensource.com/mailman/listinfo/xen-api >> >> >> > >> > >> > _______________________________________________ >> > xen-api mailing list >> > xen-api@lists.xensource.com >> > http://lists.xensource.com/mailman/listinfo/xen-api >> > >> > >> >> >> >> -- >> Marco Sinhoreli >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api >Hi, Mine is UTC-4, same as EST I guess... _______________________________________________ xen-api mailing list xen-api@lists.xensource.com http://lists.xensource.com/mailman/listinfo/xen-api