search for: kilo

Displaying 20 results from an estimated 82 matches for "kilo".

Did you mean: kill
2016 Jan 20
0
Re: channel device "state" value missing within OpenStack Kilo version
...s request , I was investigating on the wrong compute node. It works fine. Sorry for incovenience. Regards, J.P. De : Jean-Pierre Ribeauville Envoyé : mercredi 20 janvier 2016 16:18 À : 'libvirt-users@redhat.com' Objet : channel device "state" value missing within OpenStack Kilo version Hi, I've installed a OpenStack KILO all-in-one . For private need , I've to add a channel device to all my GUESTS on my compute node. It works fine (e.g. via a virsh command). Problem is that , in the xml describing the Guest , this 'state' value : <target type...
2016 Jan 20
0
channel device "state" value missing within OpenStack Kilo version
Hi, I've installed a OpenStack KILO all-in-one . For private need , I've to add a channel device to all my GUESTS on my compute node. It works fine (e.g. via a virsh command). Problem is that , in the xml describing the Guest , this 'state' value : <target type='virtio' name='agent' state='d...
2015 Oct 16
0
Update for centos-release-openstack
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The CentOS Cloud SIG ( https://wiki.centos.org/SpecialInterestGroup/Cloud ) is releasing a new OpenStack metadata package called centos-release-openstack-kilo that replaces centos-release-openstack. Metadata packages in CentOS are used to setup the repositories used by the package manager ( yum ) and the signing keys used to validate content installed from the corresponding repositories. The present metadata package, called centos-release-openstack, does...
2015 Oct 17
0
CentOS-announce Digest, Vol 128, Issue 4
...stack Message-ID: <56213E92.2050104 at centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The CentOS Cloud SIG ( https://wiki.centos.org/SpecialInterestGroup/Cloud ) is releasing a new OpenStack metadata package called centos-release-openstack-kilo that replaces centos-release-openstack. Metadata packages in CentOS are used to setup the repositories used by the package manager ( yum ) and the signing keys used to validate content installed from the corresponding repositories. The present metadata package, called centos-release-openstack, does...
2006 Dec 15
2
Bandwidth requirements for 1, 000, 000 minutes a month
...) Calls average 10 minutes in duration. ) The "busiest" hour will account for 10% of the daily total. This is how I'm figuring it... Casual observation shows that SIP setup and teardown takes about 26 UDP packets. Assuming the packets are full (512 bytes) this adds up to about 13 kilo-bytes for each call. I've heard that ulaw (including overhead) is supposed to take about 80 kilo-bits/sec. Assuming each call takes 10 minutes, each call will take 13 kilo-bytes + (80 kilo-bits * 60 * 10) or 48.13 mega-bits. Assuming (to make the math easier) 10 bits = 1 byte, each call wi...
2004 Sep 02
1
GSM codec bandwidth
I've a question about the bandwidth consumed by IAX2/GSM. According to the wiki page, the GSM codec should run about 13 kilo-bits/sec for a voice encoding. However, watching gkrellm when I initiate a call to Digium, it looks like the channel is taking a consistent 5-6 kilo-bytes/sec. That's a lot more bandwidth than it should take. Is there perhaps a setting I have wrong somethere in the conf files? I have: bandw...
2006 Apr 13
2
How to create a compact Speex library
Hi, Sorry if this a repost but I want to create the smallest Speex library possible to be put in TI's TMS320 DSP. I'm only interested in one configuration: 5.97 Kbps narrowband. What part of source code can I remove? Currently, when I compiled the version 1.1.12 libspeex.a library with the TI TMS320 and Fixed-Integer options, I get around 522Kb. I would like to reduce it to as small
2006 Apr 17
2
How to create a compact Speex library
...band. What part of source code > >> can I > >> > remove? Currently, when I compiled the version > >> 1.1.12 > >> > libspeex.a library with the TI TMS320 and > >> > Fixed-Integer options, I get around 522Kb. > >> > >> You mean kilo-bit or kilo-byte? The former is > what > >> I'd expect, so if > >> you're getting the latter, something's already > >> wrong. > >> > >> > I would > >> > like to reduce it to as small as possible given > my > >>...
2006 Apr 13
4
How to create a compact Speex library
...erested in one > configuration: > > 5.97 Kbps narrowband. What part of source code > can I > > remove? Currently, when I compiled the version > 1.1.12 > > libspeex.a library with the TI TMS320 and > > Fixed-Integer options, I get around 522Kb. > > You mean kilo-bit or kilo-byte? The former is what > I'd expect, so if > you're getting the latter, something's already > wrong. > > > I would > > like to reduce it to as small as possible given my > > above 5.97 Kbps operating constraints (I don't > need > &...
2015 Sep 17
3
Official openvswitch package for CentOS7
Hi all, Exists an official openvswitch package for CentoS7?? If I am not wrong, this: http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/openstack-neutron-openvswitch-2015.1.0-1.el7.noarch.rpm it can be used with openstack only. Do I need to recompile from source like is is explained here: https://n40lab.wordpress.com/2015/06/28/centos-7-installing-openvswitch-2-3-2-lts/ or exists another rpm package for CentOS7?? Thanks.
2012 Oct 02
8
Being strict on differentiating between IEC prefixes and SI prefixes.
...is so standards-compliant, no other framework that I have seen have complied to the HTTP standard (think REST) in such a degree that Rails does. Kudos to you all for that. I think we (Rails community) should follow the line of standards compliance and also take it to the binary prefixes [1], i.e. kilobytes, megabytes, etc. For more than half a decade SI units has been a standard (occupying the prefixes kilo, mega, ...) Since the introduction of computers the prefixes has been misused in the IT industry for powers of 1024 but used correctly (for marketing reasons) by storage manufacturers to mean...
2012 Jan 16
2
howto test a package without installation
...i, how can i play around with my first selfwritten package [*] without to install it to my debian system? I think of something like doing this: /tmp/$ R R version 2.11.1 (2010-05-31) Copyright (C) 2010 The R Foundation for Statistical Computing ISBN 3-900051-07-0 > library(/tmp/sitools) 3 * kilo [1] 3000 [*] https://github.com/jonasstein/sitools -- Jonas Stein <news at jonasstein.de>
2016 Mar 02
2
ceph and libxl errors attaching device
Dear, I need to attach some ceph (0.94.6) block devices to our openstack (kilo) running instances (xen 4.4) . Nova is able to create volumes, attach a detach (alt least there are no errors) The hypervisor can see the blockdevice: # rbd -p volumes ls volume-xxxxxxxx-7342-434b-9xx1-d046bcxxxxfd And the instance xml seems to be ok: ....................
2015 Sep 18
2
Official openvswitch package for CentOS7
....com> >> > wrote: >> >> Hi all, >> >> >> >> Exists an official openvswitch package for CentoS7?? If I am not >> >> wrong, this: >> >> >> >> >> >> http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/openstack-neutron-openvswitch-2015.1.0-1.el7.noarch.rpm >> >> >> >> it can be used with openstack only. >> >> >> >> Do I need to recompile from source like is is explained here: >> >> >> >> https://n40lab.wordpress.com/2015/06/...
2006 Apr 13
0
How to create a compact Speex library
...n TI's > TMS320 DSP. I'm only interested in one configuration: > 5.97 Kbps narrowband. What part of source code can I > remove? Currently, when I compiled the version 1.1.12 > libspeex.a library with the TI TMS320 and > Fixed-Integer options, I get around 522Kb. You mean kilo-bit or kilo-byte? The former is what I'd expect, so if you're getting the latter, something's already wrong. > I would > like to reduce it to as small as possible given my > above 5.97 Kbps operating constraints (I don't need > all the other extra features from Speex:...
2001 Sep 20
1
OT: Ogg Vorbis and Bitrate
>>>> I've heard lots of discussion about it, >>>> but what I was taught in school was kilo >>>> was greek for 1000. In most usages "kilo XXX" >>>> means "1000 of XXX". This is correct, but... >>>> In electronics terms >>>> I understand we use it collectively wrong >>>> from a linguistic accuracy point of vi...
2000 Jan 06
1
No subject
I apologize in advance to those for who this wuestion may be too stupid. Running R 0.091 on Windows 95 (a very old machine I'm afraid 486-66 16M) When constructing a big matrix I get: Error: heap memory (6144 Kb) exhausted [needed 7087 Kb more] See "help(Memory)" on how to increase the heap size. Help(Memory) tells me I must: (Quote) Use command line options to set the memory
2015 Sep 17
6
Official openvswitch package for CentOS7
...ich.edu> wrote: > On Thu, Sep 17, 2015 at 3:19 PM, C. L. Martinez <carlopmart at gmail.com> wrote: >> Hi all, >> >> Exists an official openvswitch package for CentoS7?? If I am not wrong, this: >> >> http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/openstack-neutron-openvswitch-2015.1.0-1.el7.noarch.rpm >> >> it can be used with openstack only. >> >> Do I need to recompile from source like is is explained here: >> https://n40lab.wordpress.com/2015/06/28/centos-7-installing-openvswitch-2-3-2-lts/ >> or exist...
2015 Jul 31
5
[PATCH net-next] virtio_net: add gro capability
...s/class/net/xxx/gro_flush_timeout to 1000 nsec, Rick Jones reported following results. One VM of each on a pair of OpenStack compute nodes with E5-2650Lv3 CPUs and Intel 82599ES-based NICs. So, two "before" and two "after" VMs. The OpenStack compute nodes were running OpenStack Kilo, with VxLAN encapsulation being used through OVS so no GRO coming-up the host stack. The compute nodes themselves were running a 3.14-based kernel. Single-stream netperf, CPU utilizations and thus service demands are based on intra-guest reported CPU. Throughput Mbit/s, bigger is better...
2015 Jul 31
5
[PATCH net-next] virtio_net: add gro capability
...s/class/net/xxx/gro_flush_timeout to 1000 nsec, Rick Jones reported following results. One VM of each on a pair of OpenStack compute nodes with E5-2650Lv3 CPUs and Intel 82599ES-based NICs. So, two "before" and two "after" VMs. The OpenStack compute nodes were running OpenStack Kilo, with VxLAN encapsulation being used through OVS so no GRO coming-up the host stack. The compute nodes themselves were running a 3.14-based kernel. Single-stream netperf, CPU utilizations and thus service demands are based on intra-guest reported CPU. Throughput Mbit/s, bigger is better...